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/design)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/design"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/design.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.00021 | $0.02918 |
| Opus 5 | $0.00010 | $0.01459 |
| Sonnet 5 | $0.00004 | $0.00584 |
| Haiku 4.5 | $0.00002 | $0.00292 |
Grade A, and why
workflow-design 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/workflow:design
Mission
Exécuter la phase de Conception (Solutioning) du workflow de développement. Cette phase se concentre sur la création de la Spécification Technique, la conception de l'architecture et la documentation des décisions techniques clés.
Quand utiliser
- Tracks Standard et Enterprise
- Après la complétion de
/workflow:plan - Quand le PRD et le backlog sont prêts
Prérequis
- Le PRD existe dans
project-management/prd.md - Le backlog existe dans
project-management/backlog/
Mode Plan
Le mode plan est recommandé. Claude active le mode plan pour structurer l'approche, identifier les dépendances et présenter une stratégie de génération avant de créer les artefacts.
Workflow
Étape 1 : Mise en place de la conception
╔══════════════════════════════════════════════════════════╗
║ PHASE DE CONCEPTION - DÉMARRAGE ║
╠══════════════════════════════════════════════════════════╣
║ Track: Standard ║
║ Phase: 3 sur 4 - Conception (Solutioning) ║
║ ║
║ Objectifs : ║
║ • Créer la Spécification Technique à partir du PRD ║
║ • Concevoir l'architecture système (diagrammes C4) ║
║ • Définir le modèle de données et la conception API ║
║ • Documenter les Architecture Decision Records (ADR) ║
║ • Planifier la stratégie de test ║
╚══════════════════════════════════════════════════════════╝
Étape 2 : Chargement des artefacts de planification
╔══════════════════════════════════════════════════════════╗
║ CHARGEMENT DES ARTEFACTS DE PLANIFICATION ║
╠══════════════════════════════════════════════════════════╣
║ ║
║ Analyse du PRD : ║
║ ├── ✅ prd.md chargé ║
║ ├── Exigences fonctionnelles : 12 ║
║ ├── Exigences non fonctionnelles : 8 ║
║ └── Intégrations requises : 2 ║
║ ║
║ Résumé du backlog : ║
║ ├── ✅ backlog/ chargé ║
║ ├── EPICs : 4 ║
║ ├── User Stories : 18 ║
║ └── Story Points totaux : 89 ║
║ ║
║ Contraintes (si Enterprise) : ║
║ └── ✅ analysis/constraints.md chargé ║
║ ║
╚══════════════════════════════════════════════════════════╝
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 · 289 lines · 21 tokens per session scan A f0b456be6d0f
workflow-design is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 2,918 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].