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.
git 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/status)<a href="https://agentmods.dev/commands/avanturer/claude-bestpractice/status"><img src="https://agentmods.dev/badge/commands/avanturer/claude-bestpractice/status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/avanturer/claude-bestpractice/status"><img src="https://agentmods.dev/badge/commands/avanturer/claude-bestpractice/status.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00082 |
| Opus 5.5 | $0.00006 | $0.00033 |
| Sonnet 5.5 | $0.00003 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
status 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 18d 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 status
Read the output above and tell the user, in two or three sentences, the one thing worth doing next. If the NEXT ACTION line names something, say why it matters rather than repeating it verbatim.
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.
- 18d ago Changed 58689d91e1ed
- 1mo ago First seen · 11 lines · 14 tokens per session scan A d3ef9aa801ba
status is a command published in the GitHub repository avanturer/claude-bestpractice (2 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 82 once invoked, about $0.0001 per session on Opus 5.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
flow
End-to-end feature/bug/refactor pipeline (plan → start → implement → QA → ship → address → cleanup) with an interactive gate at every phase. Resumable via /orc:resume. --jira links a ticket. Workspace-aware.
jira-breakdown
Turn a feature brief, PRD, or existing Epic into a full Jira hierarchy behind a preview gate.
jira
Manage Jira tickets via acli, and bind/unbind a ticket key to the current orc session — persists jiraTicket in .orc/orc.json + checkpoint.md so /orc:status, /orc:resume, and /orc:ship all see the link.
setup
Run-once repo interview that writes the tracker layer (docs/agents/issue-tracker.md, triage-labels.md, domain.md) with recommended answers.
postmortem
Author a blameless incident postmortem — timeline, root causes, action items — filing each P0 action item as a tracker issue. Status reaches Final only when all P0 items close.
triage
Intake for any report (issue, PR, Jira, Sentry, paste): check it is valid, then brief, file, park or reject it.