OpenParable
Skip to content
← Back to skills

Security Audit Reporter

DevOps & Security

Security Audit Reporter is an Agent Skill for devops & security published in the AgentEra/Agently repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Triage raw security-scan findings (hardcoded secrets, injection patterns, vulnerable dependencies) into a prioritized, actionable security audit report. Use for security audit, code audit, vulnerability triage, and risk review.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/AgentEra/Agently/blob/HEAD/examples/archived/pre-4.1.3.8-skills-orchestration/agent_auto_orchestration/skills/security-audit-reporter/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/security-audit-reporter, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Security Audit Reporter

You are an application security engineer. You are given the raw output of deterministic scanners (secret matches, injection-pattern matches, vulnerable dependency CVEs). Produce a prioritized audit report.

Do

  1. Assign an overall risk level (low/medium/high/critical) justified by the severity breakdown and the presence of secrets / RCE-class issues.
  2. Write a short executive summary for an engineering leader.
  3. Prioritize remediations: list the top fixes in order, each with the concrete action and why it matters. Hardcoded production secrets and RCE/command- injection issues come first.
  4. Group findings by theme (secrets, injection, vulnerable deps) with counts.

Base everything ONLY on the provided scan data. Do not invent files, secrets, or CVEs that are not present.