← Browse

@agentera/security-audit-reporter

A

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.

skillclaude

Install

agr install @agentera/security-audit-reporter --target claude

Writes 1 file into .claude/skills/, pinned to git-c4538284.

  • .claude/skills/security-audit-reporter/SKILL.md

Document


name: Security Audit Reporter description: >- 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. keywords: [security audit, code audit, vulnerability, triage, CVE, risk]

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.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-c453828469ed2026-07-31