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/delivery)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/delivery"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/delivery.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.00024 | $0.06666 |
| Opus 5 | $0.00012 | $0.03333 |
| Sonnet 5 | $0.00005 | $0.01333 |
| Haiku 4.5 | $0.00002 | $0.00667 |
Grade A, and why
delivery 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 — 551 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Équipe de Livraison - Cycle de Vie Complet du Sprint (Rédaction + Implémentation)
Orchestrer le cycle complet du sprint en utilisant les Claude Code Agent Teams (v2.1.32+). La Phase 1 rédige les EPICs, User Stories (INVEST+3C+Gherkin) et tâches avec revue croisée. La Phase 2 les implémente en parallèle en utilisant le mapping de domaines fichiers de la Phase 1. Le même Delivery Lead (opus) orchestre les deux phases, préservant le contexte complet à travers la transition.
Arguments
$ARGUMENTS
<sprint-name|prd-path>: Nom/ID du sprint ou chemin vers le document PRD--phase=all: Phase à exécuter (par défaut :all). Options :all,writing,implementation--max-workers=3: Nombre maximum de workers parallèles par phase (par défaut : 3, max : 3)--overnight: Exécuter en mode nuit (borné, s'arrête à 6h)--supervised: Pause avant chaque story pour confirmation humaine--max-stories=10: Nombre maximum de stories à traiter (par défaut : 10)--timeout=16: Durée maximale d'exécution en heures (par défaut : 16)--dry-run: Afficher la composition de l'équipe, l'estimation de coût et les assignations de stories sans exécuter--quality-threshold=6: Score INVEST minimum pour la Phase 1 (par défaut : 6/6)--max-rewrites=2: Nombre maximum de boucles de réécriture par artefact en Phase 1 (par défaut : 2)--max-cost=<dollars>: Budget maximum en dollars. Si le coût parallèle estimé dépasse ce seuil, l'exécution est bloquée avec un message OVER BUDGET
Prérequis
- Claude Code v2.1.32+ avec support Agent Teams
- Variable d'environnement
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1définie - PRD ou spécification technique disponible (pour la Phase 1) ou backlog sprint BMAD avec des stories
ready-for-dev(pour la Phase 2 uniquement) - Métadonnées du sprint dans
.bmad/sprint-status.yaml Tools/AgentTeams/lib/compatibility-check.shdisponibleTools/AgentTeams/lib/cost-estimator.shdisponibleTools/AgentTeams/lib/result-aggregator.shdisponible
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 · 551 lines · 24 tokens per session scan A 1668840101fd
delivery is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 6,666 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
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].