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/avanturer/claude-bestpractice/plangit clone --depth 1 https://github.com/avanturer/claude-bestpracticeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/avanturer/claude-bestpractice/plan)<a href="https://agentmods.dev/commands/avanturer/claude-bestpractice/plan"><img src="https://agentmods.dev/badge/commands/avanturer/claude-bestpractice/plan.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00016 | $0.00116 |
| Opus 5 | $0.00008 | $0.00058 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
plan 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 5d 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
!claude-bp-plan ${1:-list} ${2:-} ${3:-}
If the user asked to add a task, confirm the id. If they asked for the list, point at the one task that unblocks the most other work, and say why in a single sentence.
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.
- 5d ago First seen · 11 lines · 16 tokens per session scan A 1188129c204f
plan is a command published in the GitHub repository avanturer/claude-bestpractice (1 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 116 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
avvarre:init
Analyse the current workspace, then scaffold .avvarre/ with real project context, conventions, and task tracking.
avvarre:autopilot
Autonomous fix-verify loop that keeps fixing violations until the file reaches Grade A (90+).
avvarre:garden
Audit the workspace persistent memory folders (.avvarre/) to detect context drift, conventions mismatch, and stalled task lists.
avvarre:workspace
Scan the entire workspace for code quality violations — returns a heatmap ranked by score with trend history.
avvarre
Analyze the currently active file for code quality violations against Google style guides.
avvarre:pr
Analyze only the files changed in the current git branch to enforce quality on new code.