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/start)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/start"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/start.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.00007 | $0.02359 |
| Opus 5 | $0.00003 | $0.01179 |
| Sonnet 5 | $0.00001 | $0.00472 |
| Haiku 4.5 | $0.00001 | $0.00236 |
Grade A, and why
start 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 3d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Préparation du Début de Sprint
Tu es un Scrum Master expérimenté. Tu dois préparer et faciliter le démarrage d'un nouveau sprint en vérifiant que toutes les conditions sont réunies.
Arguments
$ARGUMENTS
Arguments :
- Numéro du sprint (ex:
5) - (Optionnel) Durée en jours (défaut: 10 jours = 2 semaines)
Exemple : /workflow:start 5
MISSION
Étape 1 : Vérifier les Prérequis
1.1 Sprint Précédent Clôturé
# Vérifier l'état du sprint précédent
# - Sprint Review effectuée
# - Rétrospective effectuée
# - Toutes les US terminées ou reportées
1.2 Backlog Priorisé
- Le Product Owner a priorisé le backlog
- Les US candidates sont estimées
- Les critères d'acceptance sont définis
1.3 Équipe Disponible
- Disponibilités confirmées
- Congés identifiés
- Capacité calculée
Étape 2 : Calculer la Capacité
══════════════════════════════════════════════════════════════
📊 CALCUL DE CAPACITÉ - Sprint {N}
══════════════════════════════════════════════════════════════
Durée du sprint : {X} jours ouvrés
Date début : {YYYY-MM-DD}
Date fin : {YYYY-MM-DD}
──────────────────────────────────────────────────────────────
👥 DISPONIBILITÉ ÉQUIPE
──────────────────────────────────────────────────────────────
| Membre | Jours dispo | Focus (%) | Capacité |
|--------|-------------|-----------|----------|
| Dev 1 | 10/10 | 80% | 8 jours |
| Dev 2 | 8/10 | 80% | 6.4 jours|
| Dev 3 | 10/10 | 50% | 5 jours |
| Total | - | - | 19.4 jours|
──────────────────────────────────────────────────────────────
📈 VÉLOCITÉ
──────────────────────────────────────────────────────────────
| Sprint | Points planifiés | Points livrés |
|--------|------------------|---------------|
| S-3 | 25 | 23 |
| S-2 | 28 | 26 |
| S-1 | 30 | 28 |
| Moyenne| 27.7 | 25.7 |
Vélocité moyenne : 26 points
Capacité ajustée : ~24 points (facteur sécurité 10%)
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.
- 3d ago First seen · 305 lines · 7 tokens per session scan A 595ee83995a6
start is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 2,359 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
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
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.
handoff
Create a handoff document for seamless session continuity.
todo-triage
Inventory every TODO, FIXME, HACK, and XXX comment in the codebase, enrich each with age and author from git blame, classify them into actionable buckets (bug risk, missing feature, cleanup, obsolete), and produce a prioritized triage table with recommended dispositions. Pass a path to limit the scan to a directory.…
archive
name: OpenSpec: Archive description: Archive a deployed OpenSpec change and update specs. category: OpenSpec tags: [openspec, archive].