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/thebeardedbearsas/claude-craft/statusgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/status)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/status"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/status.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.00011 | $0.01656 |
| Opus 5 | $0.00005 | $0.00828 |
| Sonnet 5 | $0.00002 | $0.00331 |
| Haiku 4.5 | $0.00001 | $0.00166 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Recette Status - Statut et Progression des Sessions
Affiche le statut et la progression des sessions QA Recette. Consultez les details d'une session individuelle ou listez toutes les sessions avec filtrage.
Arguments
$ARGUMENTS
--session=<id>: Afficher le statut detaille d'une session specifique (ex: REC-20260130-143022)--all: Lister toutes les sessions avec resume--scope=<type>: Filtrer par perimetre (story, sprint)--status=<status>: Filtrer par statut (running, completed, paused, failed)--format=<type>: Format de sortie (table, yaml, json) — defaut : table--watch: Mode rafraichissement en direct (toutes les 5 secondes)
Fonctionnalites Cles
| Fonctionnalite | Description |
|---|---|
| Liste des Sessions | Lister toutes les sessions avec statut, progression et dates |
| Vue Detaillee | Session unique avec repartition des tests, erreurs, chronometrage |
| Barres de Progression | Indicateurs visuels de progression pour les sessions en cours |
| Filtrage | Filtrer par perimetre, statut ou plage de dates |
| Mode Direct | Mode watch pour le suivi en temps reel |
| Etat de Correction | Affiche le statut fix-state.yaml si recette-fix a ete execute |
Processus
1. Decouverte des Sessions
┌─────────────────────────────────────────┐
│ 1. scan_sessions() │
│ - Lire .recette/sessions/ │
│ - Charger state.yaml par session │
│ - Charger fix-state.yaml si present │
│ - Appliquer les filtres │
└─────────────────────────────────────────┘
2. Liste des Sessions (--all)
Affiche un tableau recapitulatif :
┌──────────────────────┬────────┬──────────┬───────────┬──────────┬────────────┐
│ ID Session │ Scope │ Cible │ Statut │ Progres │ Date │
├──────────────────────┼────────┼──────────┼───────────┼──────────┼────────────┤
│ REC-20260130-143022 │ story │ US-001 │ completed │ 15/15 │ 2026-01-30 │
│ REC-20260131-091500 │ sprint │ Sprint-3 │ paused │ 8/23 │ 2026-01-31 │
│ REC-20260201-140000 │ story │ US-005 │ running │ 3/10 │ 2026-02-01 │
└──────────────────────┴────────┴──────────┴───────────┴──────────┴────────────┘
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 · 160 lines · 11 tokens per session scan A c83545c29638
status is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 1,656 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-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
implement
You are in full autonomous implementation mode. Follow the VisionAgent agentic task approach from CLAUDE.md rigorously.
e2e
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.