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.
npx agentmods add commands/starter-series/create-starter/audit-securitygit clone --depth 1 https://github.com/starter-series/create-starterWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00063 | $0.00384 |
| Opus 5 | $0.00032 | $0.00192 |
| Sonnet 5 | $0.00013 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
audit-security 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 yesterday.
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.
What it actually says
You are auditing the repo's supply chain + CI security hygiene as a complement to Anthropic's in-session claude-security-guidance plugin (in-session guard) and claude-code-security-review Action (post-PR review).
Steps
- Call the
audit_securityMCP tool withpathset to the absolute path of the repo. If no path is given, use the MCP server's cwd. - Surface the verdict (
hardened/needs-attention/soft) and the table of checks:- present / partial / missing / not-applicable
- Evidence (workflow files, config presence, gh-api result)
- Recommendation (for non-present items)
- For each
missingorpartial, propose the concrete add (workflow snippet, repo setting viagh api).
Positioning
- In-session guard (Anthropic
claude-security-guidanceplugin, released 2026-05-26): catches vulnerabilities as code is written. - Post-PR AI review (
anthropics/claude-code-security-reviewAction): reviews diffs on PR. - Repo-level audit (
audit_security, this tool): verifies the static CI baseline is present and pinned.
These three are complementary. Recommend installing all three when missing.
Do NOT
- Modify the repo or repo settings. Suggest the
gh apiPATCH commands; let the user run them.
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.
- yesterday First seen · 28 lines · 63 tokens per session scan A 308aea961ef6
audit-security is a command published in the GitHub repository starter-series/create-starter (1 stars, last pushed 14d ago), licensed MIT. It adds 63 tokens to every session and 384 once invoked, about $0.0003 per session on Opus 5. 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.
Other commands, from other repositories
test-e2e
Write end-to-end tests for critical user journeys.
test-integration
Write integration tests for component boundaries.
export
Design public API exports.
newpkg
Generate new package with Nx.
init
Initialize goal-flight state for a project.
index
Command "index" from cesarandreslopez/tauri-agent-tools, covering command reference, command summary, categories, visual capture and dom inspection.