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/auto-sprint)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/auto-sprint"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/auto-sprint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/auto-sprint"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/auto-sprint.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.02920 |
| Opus 5 | $0.00016 | $0.01460 |
| Sonnet 5 | $0.00007 | $0.00584 |
| Haiku 4.5 | $0.00003 | $0.00292 |
Grade A, and why
auto-sprint 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 5d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Sprint — Orchestrateur de Sprint de Bout en Bout
Tu joues le rôle de Product Owner / Scrum Master et tu pilotes un sprint complet, du lancement au merge,
en une seule commande. Chaque cérémonie s'exécute dans un sous-agent isolé : la fenêtre de contexte
propre au sous-agent remplace le /clear manuel entre les étapes, ce qui permet à ton contexte d'orchestrateur
de rester léger. La phase d'implémentation est conduite par toi en tant que chef d'orchestre (même logique
que /team:sprint) afin d'éviter l'imbrication d'Agent Teams.
Cette commande automatise ce qui nécessitait auparavant six commandes manuelles avec un /clear entre chaque :
/workflow:start N -> /project:decompose-tasks 00N -> /gate:validate-sprint 00N
-> /team:sprint "sprint-00N" -> /workflow:review N -> /workflow:retro N
…et ajoute : branche, commit, Pull Request, surveillance CI et merge.
Arguments
$ARGUMENTS
<N>: Numéro du sprint (ex.5). Obligatoire.--auto-merge: Merge automatiquement dès que la CI est verte et que la DoD est validée. Défaut : DÉSACTIVÉ — la commande se met en pause et attend un GO humain explicite avant de merger (respecte la règle de « revue obligatoire », règle 09, et le principe Karpathy « pas d'auto-merge sans revue humaine »).--max-fix-attempts=2: Nombre maximal de tentatives de correction automatique par gate échoué avant abandon (défaut : 2).--max-workers=3: Nombre maximal de workers dev parallèles pendant la phase d'implémentation (défaut : 2, max : 3).--base=main: Branche de base pour la PR (défaut :main).--dry-run: Affiche les 9 phases planifiées et le contexte de sprint résolu, puis s'arrête. Aucune écriture.--overnight: Transmis à la phase d'implémentation (borné, s'arrête à 6h).
Prérequis
- Claude Code v2.1.32+ avec le support Agent Teams
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1défini- CLI
ghauthentifié (création de PR / checks / merge) - Docker disponible (tous les tests s'exécutent via Docker — voir le CLAUDE.md du projet)
- Projet BMAD v6 avec
.bmad/sprint-status.yamlprésent
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.
- 5d ago First seen · 198 lines · 33 tokens per session scan A 1c4d16af458d
auto-sprint is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 2,920 once invoked, about $0.0002 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…