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/benmarte/autoimprove/auditgit clone --depth 1 https://github.com/benmarte/autoimproveWhat 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.00012 | $0.00111 |
| Opus 5 | $0.00006 | $0.00056 |
| Sonnet 5 | $0.00002 | $0.00022 |
| Haiku 4.5 | $0.00001 | $0.00011 |
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.
What it actually says
Run the audit skill to scan the codebase and generate a prioritized deficiency report.
The audit will:
- Measure your current score across all metrics
- Count individual issues (type errors, failing tests, lint warnings)
- Rank areas by efficiency (points gained per iteration)
- Show estimated iterations and token usage to reach 100%
- Optionally start fixing — area by area, interactively
No arguments needed. The audit always scans everything.
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.
- 2d ago First seen · 15 lines · 12 tokens per session scan A 940961678b6b
audit is a command published in the GitHub repository benmarte/autoimprove (5 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 111 once invoked, about $0.0001 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
crossframe-essay
使用 CrossFrame Essay 把用户给出的主题、素材或问题写成中文批判性洞察文章。.
crossframe-max
Use CrossFrame Max only when the user explicitly asks for maximum CrossFrame mode, exhaustive structural projection, full-scale world-model interpretation, or no word-limit complete explanation.
crossframe-suite
Use this command when a CrossFrame task needs multiple sibling skills in sequence.
crossframe-history
Use CrossFrame History for historical materials, civilization continuity, source-ledger boundaries, dynasty or institutional history, archive-access backlog, FOIA closeout, or local C5 boundary summaries.
crossframe-inquiry
Use CrossFrame Inquiry after a completed CrossFrame diagnosis, article, review, or suite workflow when the user wants follow-up questions, counterexamples, missing evidence, transfer conditions, or action boundaries.
crossframe-notebook
Use CrossFrame Notebook for bidirectional reading notes on books, essays, theories, excerpts, or citations.