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/analyze)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/analyze"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/analyze.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.00020 | $0.01997 |
| Opus 5 | $0.00010 | $0.00999 |
| Sonnet 5 | $0.00004 | $0.00399 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
workflow-analyze 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/workflow:analyze
Mission
Exécuter la phase d'Analyse du workflow Enterprise. Cette phase se concentre sur la recherche, l'exploration et l'identification des contraintes avant que la planification détaillée ne commence.
Quand utiliser
- Projets sur le track Enterprise
- Nouvelles plateformes ou initiatives majeures
- Quand la connaissance du domaine est limitée
- Avant de s'engager sur une approche technique
Mode Plan
Le mode plan est activé automatiquement lorsque le périmètre couvre plusieurs modules ou nécessite une investigation transversale.
Workflow
Étape 1 : Mise en place de l'analyse
╔══════════════════════════════════════════════════════════╗
║ PHASE D'ANALYSE - DÉMARRAGE ║
╠══════════════════════════════════════════════════════════╣
║ Track: Enterprise ║
║ Phase: 1 sur 4 - Analyse ║
║ ║
║ Objectifs : ║
║ • Comprendre le domaine du problème ║
║ • Rechercher les solutions existantes ║
║ • Identifier les contraintes techniques ║
║ • Documenter les risques et opportunités ║
╚══════════════════════════════════════════════════════════╝
Étape 2 : Domaines de recherche
Questions de recherche guidées :
┌─────────────────────────────────────────────────────────┐
│ RECHERCHE DOMAINE │
├─────────────────────────────────────────────────────────┤
│ 1. Quel problème résolvons-nous ? │
│ 2. Qui sont les parties prenantes clés ? │
│ 3. Quels sont les moteurs business ? │
│ 4. À quoi ressemble le succès ? │
└─────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────┐
│ RECHERCHE MARCHÉ │
├─────────────────────────────────────────────────────────┤
│ 1. Quelles solutions existantes existent ? │
│ 2. Que font les concurrents ? │
│ 3. Quelles sont les bonnes pratiques du secteur ? │
│ 4. Quelles sont les tendances émergentes ? │
└─────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────┐
│ RECHERCHE TECHNIQUE │
├─────────────────────────────────────────────────────────┤
│ 1. Quelles technologies pourrions-nous utiliser ? │
│ 2. Quels sont les besoins d'intégration ? │
│ 3. Quels sont les besoins de scalabilité ? │
│ 4. Quelles exigences sécurité/conformité existent ? │
└─────────────────────────────────────────────────────────┘
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 · 214 lines · 20 tokens per session scan A 96ed3871de75
workflow-analyze is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,997 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.