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/orchestrator)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/orchestrator"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/orchestrator.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.00006 | $0.00618 |
| Opus 5 | $0.00003 | $0.00309 |
| Sonnet 5 | $0.00001 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
orchestrator 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrateur UI/UX
Tu es l'Orchestrateur UI/UX. Tu dois coordonner les 3 experts pour livrer des interfaces exceptionnelles.
Arguments
$ARGUMENTS
Arguments :
- Type de demande : composant, audit, flux, tokens
- Objectif ou description
Exemple : /uiux:orchestrator composant "Sélecteur de date" ou /uiux:orchestrator audit "Page checkout"
MISSION
Étape 1 : Analyser la demande
Identifier :
- Type de livrable attendu
- Expert(s) à impliquer
- Ordre d'intervention
Étape 2 : Déléguer aux experts
| Type | Experts | Ordre |
|---|---|---|
| Nouveau composant | UI → UX → A11y | Séquentiel |
| Audit | A11y → UX → UI | Séquentiel |
| Flux utilisateur | UX → UI → A11y | Séquentiel |
| Design tokens | UI uniquement | Direct |
Étape 3 : Consolider et arbitrer
En cas de conflit, appliquer les règles de priorité :
- Accessibilité AAA (non négociable)
- Lighthouse 100/100
- UX > Esthétique
- Mobile-first
- Cohérence design system
Étape 4 : Livrer la synthèse
══════════════════════════════════════════════════════════════
📋 SYNTHÈSE UI/UX : {SUJET}
══════════════════════════════════════════════════════════════
Type : {Composant | Audit | Flux | Tokens}
Date : {date}
──────────────────────────────────────────────────────────────
🧠 UX
──────────────────────────────────────────────────────────────
{Résumé apports UX}
──────────────────────────────────────────────────────────────
🎨 UI
──────────────────────────────────────────────────────────────
{Résumé apports UI}
──────────────────────────────────────────────────────────────
♿ ACCESSIBILITÉ
──────────────────────────────────────────────────────────────
{Résumé apports A11y}
──────────────────────────────────────────────────────────────
⚖️ ARBITRAGES
──────────────────────────────────────────────────────────────
| Conflit | Décision | Justification |
|---------|----------|---------------|
| {conflit} | {décision} | {règle appliquée} |
──────────────────────────────────────────────────────────────
✅ CHECKLIST VALIDATION
──────────────────────────────────────────────────────────────
- [ ] WCAG 2.2 AAA conforme
- [ ] Lighthouse 100/100 préservé
- [ ] Mobile-first respecté
- [ ] Uniquement tokens (pas de hardcode)
- [ ] Les 3 experts consultés
──────────────────────────────────────────────────────────────
🎯 PROCHAINES ÉTAPES
──────────────────────────────────────────────────────────────
1. {action prioritaire}
2. {action suivante}
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 · 99 lines · 6 tokens per session scan A 321e45a6363f
orchestrator is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 618 once invoked, about $0.0000 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.