audit

A command that checks a project or selected files for security problems using the OWASP Top 10, a common list of major web-application risks.

In plain words
What is it for?
Use it to find exposed keys, SQL or command injection, cross-site scripting, and authentication or permission problems across a file, directory, or project.
Why use it?
It gives you a structured security report with severity levels, attack examples, and suggested fixes instead of an unorganized list of warnings.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/flasherses/claude-code-dotfiles/audit
Clone the repo
git clone --depth 1 https://github.com/flasherses/claude-code-dotfiles
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 233 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00233
Opus 5 $0.00000 $0.00117
Sonnet 5 $0.00000 $0.00047
Haiku 4.5 $0.00000 $0.00023

Measured 2d ago against content hash d98a69e8b15a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/audit.md · 33 lines

What it actually says

/audit — 安全审计

对指定文件或项目执行全面安全审计。

用法

/audit [文件或目录路径]

不指定路径时,审计整个当前工作目录。

执行流程

  1. 确定审计范围

    • 如果提供了 $ARGUMENTS,审计指定文件
    • 否则审计当前目录下所有源代码文件
  2. 安全审计 — 调起 security-auditor 子代理

    • 按 OWASP Top-10 逐项扫描
    • 硬编码密钥检测
    • 注入漏洞扫描(SQL/XSS/命令)
    • 认证与授权检查
  3. 输出报告 — 按严重等级分组(Critical / High / Medium / Info)

输出

  • 审计文件数
  • 按 CWE 编号分组的问题清单
  • 每个问题的攻击场景和修复建议
  • 整体风险评估:LOW / MEDIUM / HIGH / CRITICAL
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 33 lines · 0 tokens per session scan A d98a69e8b15a

Subscribe to this mod's changes

audit is a command published in the GitHub repository flasherses/claude-code-dotfiles (5 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 233 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.