security-audit

A command that performs a security review of the current codebase. It looks for vulnerabilities, unsafe configuration, exposed secrets, authentication problems, and produces a prioritized report.

In plain words
What is it for?
Use it to check an existing project for code vulnerabilities, configuration mistakes, leaked secrets, and authentication flaws.
Why use it?
It brings security issues together in one review and indicates which problems should be addressed first.

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/mattdgn/config_cc/security-audit
Clone the repo
git clone --depth 1 https://github.com/Mattdgn/config_cc
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,893 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00032 $0.01893
Opus 5 $0.00016 $0.00946
Sonnet 5 $0.00006 $0.00379
Haiku 4.5 $0.00003 $0.00189

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

Security

Grade A, and why

security-audit scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

grep -rn --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" -E "(eval\(|exec\(|execSync\(|child_process|dangerouslySetInnerHTML|innerHTML\s*=|\.raw\(|unsafeWindow)" . --exclude-dir=node_modules --exclu
commands/security-audit.md · 207 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 207 lines · 32 tokens per session scan A 08b271d60c83

Subscribe to this mod's changes

security-audit is a command published in the GitHub repository Mattdgn/config_cc (2 stars, last pushed 5mo ago), with no licence file. It adds 32 tokens to every session and 1,893 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.