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/reportgit 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/report)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/report"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/report.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.1 | $0.00014 | $0.01527 |
| Opus 5 | $0.00007 | $0.00763 |
| Sonnet 5 | $0.00003 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00153 |
Grade A, and why
report 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Recette Report - Generation de Rapports
Genere des rapports detailles a partir des donnees de session QA Recette. Supporte plusieurs formats de sortie et la comparaison de sessions.
Arguments
$ARGUMENTS
--session=<id>: ID de session pour generer le rapport [requis]--format=<type>: Format de sortie (md, html, json) — defaut : md--output=<path>: Chemin de sortie personnalise (defaut :.recette/reports/)--include-screenshots: Integrer les captures d'ecran dans le rapport HTML--compare=<id>: Comparer avec une autre session pour un rapport de differences
Fonctionnalites Cles
| Fonctionnalite | Description |
|---|---|
| Multi-Format | Generer des rapports Markdown, HTML ou JSON |
| Comparaison de Sessions | Comparer deux executions pour detecter les regressions |
| Section Regle d'Or | Section dediee a la conformite dans les rapports |
| Integration de Captures | Integrer les captures d'ecran d'erreurs dans les rapports HTML |
| Tracabilite des Tests | Tracabilite complete des AC aux resultats de tests |
| Resume des Metriques | Taux de reussite/echec, chronometrage, classification des erreurs |
Processus
1. Collecte des Donnees
┌─────────────────────────────────────────┐
│ 1. load_session_data(session_id) │
│ - Lire .recette/sessions/{id}/ │
│ - Charger state.yaml │
│ - Charger fix-state.yaml si present │
│ - Collecter captures et logs │
│ - Charger le registre de regression │
└─────────────────────────────────────────┘
2. Generation du Rapport
┌─────────────────────────────────────────┐
│ 2. generate_report(format) │
│ - Construire la section resume │
│ - Construire les resultats de tests │
│ - Construire les details d'erreurs │
│ - Construire les tests de regression│
│ - Construire la declaration Regle │
│ d'Or │
│ - Appliquer le template de format │
│ - Ecrire au chemin de sortie │
└─────────────────────────────────────────┘
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 · 152 lines · 14 tokens per session scan A 431ac1648ce7
report is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,527 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.
ocr
One-shot OCR — scanned PDF to Word + WeChat HTML + audit trail.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.