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/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/review)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/review"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/review.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.00004 | $0.02319 |
| Opus 5 | $0.00002 | $0.01159 |
| Sonnet 5 | $0.00001 | $0.00464 |
| Haiku 4.5 | $0.00000 | $0.00232 |
Grade A, and why
review 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Préparation Sprint Review
Tu es un Scrum Master expérimenté. Tu dois préparer et faciliter la Sprint Review en rassemblant les informations sur le travail accompli.
Arguments
$ARGUMENTS
Arguments :
- Numéro du sprint
Exemple : /workflow:review 5
MISSION
Étape 1 : Collecter les Données du Sprint
# Récupérer les commits du sprint
git log --since="YYYY-MM-DD" --until="YYYY-MM-DD" --oneline
# PRs mergées
gh pr list --state merged --search "merged:YYYY-MM-DD..YYYY-MM-DD"
# Issues fermées
gh issue list --state closed --search "closed:YYYY-MM-DD..YYYY-MM-DD"
Étape 2 : Analyser le Sprint Backlog
══════════════════════════════════════════════════════════════
📊 SPRINT REVIEW - Sprint {N}
══════════════════════════════════════════════════════════════
Date : {YYYY-MM-DD}
Sprint Goal : "{Objectif}"
──────────────────────────────────────────────────────────────
🎯 ATTEINTE DU SPRINT GOAL
──────────────────────────────────────────────────────────────
Sprint Goal atteint : ✅ OUI / ❌ NON / ⚠️ PARTIELLEMENT
Justification : {Explication}
──────────────────────────────────────────────────────────────
📦 USER STORIES LIVRÉES
──────────────────────────────────────────────────────────────
| ID | Titre | Points | Demo | Status |
|----|-------|--------|------|--------|
| US-045 | Inscription utilisateur | 5 | ✅ | ✅ Livré |
| US-046 | Login OAuth Google | 8 | ✅ | ✅ Livré |
| US-047 | Login OAuth GitHub | 5 | ✅ | ✅ Livré |
| US-048 | Reset mot de passe | 3 | ⏳ | ⚠️ 80% |
**Livré : 18/21 points (86%)**
──────────────────────────────────────────────────────────────
❌ USER STORIES NON TERMINÉES
──────────────────────────────────────────────────────────────
| ID | Titre | Points | Avancement | Raison |
|----|-------|--------|------------|--------|
| US-048 | Reset mot de passe | 3 | 80% | API mail non dispo |
Action : Reporter au Sprint {N+1}
──────────────────────────────────────────────────────────────
📈 MÉTRIQUES
──────────────────────────────────────────────────────────────
| Métrique | Valeur | Tendance |
|----------|--------|----------|
| Points planifiés | 21 | - |
| Points livrés | 18 | - |
| Vélocité | 18 | ↗️ (+2 vs S-1) |
| Taux de complétion | 86% | ↗️ |
| Bugs découverts | 2 | ↘️ |
| Bugs corrigés | 3 | ↗️ |
──────────────────────────────────────────────────────────────
🎬 DÉMONSTRATION
──────────────────────────────────────────────────────────────
## Ordre de démo suggéré
1. **US-045 : Inscription utilisateur** (~5 min)
- Montrer le formulaire d'inscription
- Email de confirmation
- Activation du compte
- Démo par : @dev1
2. **US-046 : Login OAuth Google** (~5 min)
- Bouton "Se connecter avec Google"
- Flux OAuth
- Création compte automatique
- Démo par : @dev2
3. **US-047 : Login OAuth GitHub** (~3 min)
- Même flux avec GitHub
- Démo par : @dev1
## Scénario de démo
```gherkin
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.
- 4d ago First seen · 331 lines · 4 tokens per session scan A c981ba20de19
review is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 4 tokens to every session and 2,319 once invoked, about $0.0000 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
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
deploy
Deploy application with pre/post-deploy checks.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
update-docs
Scan for recently modified files and update corresponding documentation.
create-task-list-for-issue.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
clean-branches
List local Git branches that have been fully merged or are stale and delete them safely after showing what would be removed. Protects main, master, develop, and the currently checked-out branch. Pass --dry-run to preview without deleting anything. Distinct from the finish-branch skill, which closes a single active…