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/security)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/security"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/security/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/security"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/security.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.00020 | $0.04286 |
| Opus 5.5 | $0.00008 | $0.01714 |
| Sonnet 5.5 | $0.00004 | $0.00857 |
| Haiku 4.5 | $0.00002 | $0.00429 |
Grade A, and why
security 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 1mo 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Équipe de Revue de Sécurité - Audit de Sécurité Multi-Dimension Parallèle
Orchestrer un audit de sécurité complet en utilisant les Claude Code Agent Teams (v2.1.32+). Lance un security lead (opus) plus 3 reviewers haiku spécialisés, chacun analysant une dimension de sécurité différente en parallèle : vulnérabilités du code source, dépendances/chaîne d'approvisionnement, et infrastructure/configuration.
Arguments
$ARGUMENTS
--scope=full: Périmètre de l'audit (par défaut :full). Options :full,code,deps,infra--max-workers=3: Nombre maximum de reviewers parallèles (par défaut : 3, max : 3)--severity=medium: Sévérité minimum à rapporter :low,medium,high,critical--output-dir=<path>: Répertoire de sortie personnalisé pour les résultats de sécurité--dry-run: Afficher la composition de l'équipe et le plan de scan sans exécuter--sarif: Sortir les résultats au format SARIF (pour intégration CI/CD)--max-cost=<dollars>: Budget maximum en dollars. Si le coût parallèle estimé dépasse ce seuil, l'exécution est bloquée avec un message OVER BUDGET
Prérequis
- Claude Code v2.1.32+ avec support Agent Teams
- Variable d'environnement
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1définie - Docker disponible pour exécuter les scanners de sécurité
Tools/AgentTeams/lib/compatibility-check.shdisponibleTools/AgentTeams/lib/result-aggregator.shdisponibleTools/AgentTeams/lib/cost-estimator.shdisponible
ℹ️ Ces scripts sont installés automatiquement par claude-craft (
make install-agentteamsou via l'installeur). S'ils sont absents, la commande continue en mode dégradé : estimation de coût manuelle et--ralph-modeindisponible (non bloquant).
Garde-Fou Fast Mode (Confirmation Bloquante)
OBLIGATOIRE : Avant de lancer l'équipe, le security lead DOIT :
- Détecter si le Fast Mode est actif (indicateur lightning bolt dans le terminal)
- Si Fast Mode actif :
- Afficher le dashboard comparatif standard vs fast via
cost-estimator.sh --fast-mode - Afficher un avertissement bloquant avec les coûts comparés :
⚠️ FAST MODE DÉTECTÉ — Coûts Opus 6x plus élevés ! | Mode | Input ($/M) | Output ($/M) | Coût estimé cette revue | |----------|-------------|--------------|------------------------| | Standard | $5.00 | $25.00 | ~$X.XX | | Fast | $30.00 | $150.00 | ~$Y.YY | Voulez-vous continuer en Fast Mode ? (oui/non) Recommandation : tapez /fast pour désactiver avant de continuer. - Attendre la confirmation explicite de l'utilisateur avant de poursuivre
- Si l'utilisateur refuse, abandonner avec un message suggérant
/fastpour désactiver
- Afficher le dashboard comparatif standard vs fast via
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.
- 1mo ago First seen · 381 lines · 20 tokens per session scan A 62b8dabeb69a
security is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 4,286 once invoked, about $0.0001 per session on Opus 5.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
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
handoff
Write a session handoff document for continuity.
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.