Skip to content
SkillModel-led2,988 tokens in use

security-audit-static

A static security audit for AI-built code: maps entry points to sinks, compares documented intent with the code, tries to refute each candidate and ends with OWASP Top 10 coverage.

680 stars on the repository MIT Licensephuryn/product-engineering · ai-shipping/skills/security-audit-static
claude plugin install ai-shipping@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing security-audit-static costs

42tokens idle
2,988tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldeclared and detectedwrites filesdeclared and detected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure11/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

security-audit-static reads every file in scope in full, maps entry points such as handlers, webhooks and queue consumers to sinks such as raw SQL, shell, HTML rendering, outbound fetches and LLM prompts, and traces whether an attacker can influence each value.

Candidates are then self-refuted against cited evidence and only survivors are reported, each quoting the code it accuses with an attack scenario and fix. It runs only when a security audit is requested, and findings are code-review results, not confirmed exploits.

What You Get

  • Findings grouped by file and sorted by severity, each with verbatim evidence, risk level, step-by-step attack scenario, impact and a concrete fix
  • An OWASP Top 10 2021 coverage record marking each category with no finding as examined or not examined
  • Root causes, what is well built, and what could not be verified
  • A report model-mix note saying which clusters ran on which model, and a file written under reports/security_audit_{timestamp}.md

Common Use Cases

  • Auditing a release’s changes and what they newly reach
  • A whole-repository pass before a first release or after a large refactor
  • Checking service-role database clients for missing org or owner filters
  • Reviewing AI features for prompt injection and confused-deputy tool calls

What Makes It Unique

It keeps a candidate unless cited evidence at file and line refutes it, and bars attacker-equals-victim refutation for SSRF, billing, data-exposure and cross-tenant flows. It carries a high-miss checklist for AI-built apps: disabled row-level security, forgeable cron or bot signals, parser differentials, fail-open fallbacks, secrets in logs and prompt injection. Content that tries to steer the auditor is itself a finding.

Under The Hood

A single markdown file whose tool allowlist covers read, search, glob, subagent fan-out, git status and writing under reports. The agent reads source files, may start parallel subagents on the strongest available model, and writes one markdown report. It never edits the audited code. Other git commands ask first because log, diff and show can write with an output flag. It calls no web services and runs no scripts. The method is adapted from Anthropic’s public security-guidance plugin.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers