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.
npx agentmods add commands/thebeardedbearsas/claude-craft/plangit 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/plan)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/plan"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/plan.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 | $0.00022 | $0.02039 |
| Opus 5 | $0.00011 | $0.01019 |
| Sonnet 5 | $0.00004 | $0.00408 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
workflow-plan 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 yesterday.
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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/workflow:plan
Mission
Exécuter la phase de Planification du workflow de développement. Cette phase se concentre sur la création du Document d'Exigences Produit (PRD), la définition des personas et la génération du backlog produit initial.
Quand utiliser
- Tracks Standard et Enterprise
- Après
/workflow:init(ou/workflow:analyzepour Enterprise) - Quand on démarre la planification d'une fonctionnalité
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 planification
╔══════════════════════════════════════════════════════════╗
║ PHASE DE PLANIFICATION - DÉMARRAGE ║
╠══════════════════════════════════════════════════════════╣
║ Track: Standard ║
║ Phase: 2 sur 4 - Planification ║
║ ║
║ Objectifs : ║
║ • Créer ou mettre à jour le Document d'Exigences Produit ║
║ • Définir les personas utilisateurs ║
║ • Générer le backlog produit avec des user stories ║
║ priorisées ║
║ • Définir les métriques de succès et les KPI ║
╚══════════════════════════════════════════════════════════╝
Étape 2 : Vérification des artefacts existants
╔══════════════════════════════════════════════════════════╗
║ VÉRIFICATION DES ARTEFACTS EXISTANTS ║
╠══════════════════════════════════════════════════════════╣
║ ║
║ Vérification de project-management/ ... ║
║ ║
║ PRD : ║
║ ├── ❌ prd.md Non trouvé ║
║ ║
║ Personas : ║
║ ├── ❌ personas.md Non trouvé ║
║ ║
║ Backlog : ║
║ ├── ❌ backlog/ Non trouvé ║
║ ║
║ Analyse (Enterprise) : ║
║ ├── ✅ analysis/constraints.md Disponible ║
║ └── ✅ analysis/research.md Disponible ║
║ ║
╚══════════════════════════════════════════════════════════╝
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.
- yesterday First seen · 231 lines · 22 tokens per session scan A a028360ee719
workflow-plan is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 2,039 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
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.