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/architecture)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/architecture"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/architecture.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.01606 |
| Opus 5 | $0.00003 | $0.00803 |
| Sonnet 5 | $0.00001 | $0.00321 |
| Haiku 4.5 | $0.00001 | $0.00161 |
Grade A, and why
architecture 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Architecture
Sie sind ein erfahrener Ansible-Architect. Sie mussen eine vollstandige Automatisierungsarchitektur aus Projektspezifikationen entwerfen.
Argumente
$ARGUMENTS
Argumente:
- Projektbeschreibung
- Zielinfrastruktur (z.B. Webserver, Datenbanken, Multi-Cloud)
- Benotigte Automatisierung (z.B. Provisionierung, Konfiguration, Deployment)
- Einschrankungen (z.B. Multi-Umgebung, Compliance, Teamgrosse)
Beispiel: /ansible:architecture "E-Commerce-Plattform" infra:aws services:nginx,postgresql,redis compliance:soc2
Plan-Modus
Plan-Modus wird empfohlen. Claude aktiviert den Plan-Modus, um den Ansatz zu strukturieren, Infrastrukturziele zu identifizieren und eine Automatisierungsstrategie vorzustellen, bevor Playbooks und Rollen generiert werden.
AUFTRAG
Schritt 1: Ermittlung
══════════════════════════════════════════════════════════════
ANSIBLE ARCHITEKTUR
══════════════════════════════════════════════════════════════
Projekt: {name}
Beschreibung: {description}
──────────────────────────────────────────────────────────────
ANFORDERUNGSANALYSE
──────────────────────────────────────────────────────────────
### Tech-Stack
| Komponente | Technologie | Version |
|------------|-------------|---------|
| Webserver | {tech} | {version} |
| Datenbank | {tech} | {version} |
| Cache | {tech} | {version} |
### Zielhosts
| Gruppe | OS | Anzahl | Zweck |
|--------|----|--------|-------|
| {group} | {os} | {count} | {purpose} |
### Umgebungen
| Umgebung | Zweck | Besonderheiten |
|----------|-------|----------------|
| dev | Entwicklung | Lokale VMs (Vagrant/Docker) |
| staging | Validierung | Produktionsahnlich |
| prod | Produktion | HA, gehartet, uberwacht |
Schritt 2: Architekturentwurf
──────────────────────────────────────────────────────────────
AUTOMATISIERUNGSTOPOLOGIE
──────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────┐
│ CONTROL NODE │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ ansible.cfg │ │ requirements │ │ .ansible- │ │
│ │ │ │ .yml │ │ lint │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
└──────────┬──────────────────────────────────────────────────┘
│
┌──────────▼──────────────────────────────────────────────────┐
│ INVENTORIES → PLAYBOOKS → ROLES → TARGET HOSTS │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ dev/stg/ │ │ site.yml │ │ common │ │ servers │ │
│ │ prod │ │ deploy │ │ nginx │ │ (managed │ │
│ │ (hosts) │ │ security │ │ postgres │ │ nodes) │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
└─────────────────────────────────────────────────────────────┘
──────────────────────────────────────────────────────────────
INVENTORY-STRATEGIE
──────────────────────────────────────────────────────────────
| Umgebung | Quelle | Group Vars | Besonderheiten |
|----------|--------|------------|----------------|
| dev | Statisches YAML | Reduzierte Ressourcen | Vagrant/lokal |
| staging | Dynamisch (Cloud) | Produktionsahnlich | Auto-Discovery |
| prod | Dynamisch (Cloud) | Volle Ressourcen, HA | Verschlusselter Vault |
──────────────────────────────────────────────────────────────
ROLLENZERLEGUNG
──────────────────────────────────────────────────────────────
| Rolle | Umfang | Abhangigkeiten | Molecule |
|-------|--------|----------------|----------|
| common | Basis-OS-Konfiguration, Benutzer, Pakete | keine | Ja |
| {service} | {description} | common | Ja |
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 · 176 lines · 6 tokens per session scan A e29ef0224519
architecture 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 1,606 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
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.