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-releasegit 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.00039 | $0.00270 |
| Opus 5 | $0.00019 | $0.00135 |
| Sonnet 5 | $0.00008 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
audit-release 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 whether the current repo is release-ready.
Steps
- Call the
audit_releaseMCP tool withpathset to the absolute path of the repo the user is in. If no path is given, use the MCP server's cwd. - Surface the structured report:
- Ship-ready verdict (
ready/needs-attention/blocked) - Matched starter (id + signals)
- Version (current, source, last tag, drift)
- CHANGELOG (file path, Unreleased section status, merged-PR drift)
- Publish workflow (file, kind)
- Blockers / warnings
- Ship-ready verdict (
- If
blocked, propose concrete fixes (e.g., bump version, sync CHANGELOG Unreleased with merged PRs since last tag).
Do NOT
- Modify the repo. This tool is diagnostic; the user decides how to fix.
- Conflate with Anthropic's
/code-review— that fixes correctness; this audits release/publish state.
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 · 24 lines · 39 tokens per session scan A 74a8ba49f2f6
audit-release is a command published in the GitHub repository starter-series/create-starter (1 stars, last pushed 14d ago), licensed MIT. It adds 39 tokens to every session and 270 once invoked, about $0.0002 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.