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/deploy-setupgit 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/deploy-setup)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/deploy-setup"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/deploy-setup.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.00008 | $0.01385 |
| Opus 5 | $0.00004 | $0.00692 |
| Sonnet 5 | $0.00002 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
deploy-setup 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Deploy Setup
Sie sind ein Ansible-Deployment-Spezialist. Sie mussen eine vollstandige CI/CD-Pipeline fur die Ansible-Playbook-Ausfuhrung konfigurieren.
Argumente
$ARGUMENTS
Argumente:
- Plattformbeschreibung
- (Optional) CI-Tool: github-actions, gitlab-ci (Standard: github-actions)
- (Optional) Controller: awx, semaphore, none
Beispiel: /ansible:deploy-setup "Web-Infrastruktur" ci:github-actions controller:awx
Plan-Modus
Plan-Modus ist obligatorisch. Vor der Ausfuhrung aktiviert Claude den Plan-Modus, um das Projekt zu analysieren, eine Pipeline-Strategie vorzuschlagen und auf Validierung zu warten.
AUFTRAG
Schritt 1: Projekt analysieren
══════════════════════════════════════════════════════════════
ANSIBLE DEPLOY SETUP
══════════════════════════════════════════════════════════════
Projekt: {name}
──────────────────────────────────────────────────────────────
STACK-ERKENNUNG
──────────────────────────────────────────────────────────────
| Komponente | Erkannt | Details |
|------------|---------|---------|
| Playbooks | {count} | {paths} |
| Rollen | {count} | {names} |
| Collections | {count} | {names} |
| Vault-Nutzung | {ja/nein} | {verschlusselte Dateien} |
| Inventories | {count} | {Umgebungen} |
| Molecule-Tests | {ja/nein} | {Szenarien} |
Schritt 2: Pipeline entwerfen
──────────────────────────────────────────────────────────────
PIPELINE-STRATEGIE
──────────────────────────────────────────────────────────────
CI-Tool: {GitHub Actions / GitLab CI}
Controller: {AWX / Semaphore / Keiner}
Pipeline:
Push / PR
→ Lint: ansible-lint + yamllint
→ Test: molecule converge + verify
→ Testlauf: ansible-playbook --check --diff
→ Deploy Staging: Playbook gegen Staging ausfuhren
→ Freigabe-Gate: Manuelle Freigabe fur Produktion
→ Deploy Prod: Playbook gegen Produktion ausfuhren
──────────────────────────────────────────────────────────────
STRATEGIEAUSWAHL
──────────────────────────────────────────────────────────────
| Stufe | Tool | Ausloser | Artefakte |
|-------|------|----------|-----------|
| Lint | ansible-lint | Bei Push/PR | Lint-Bericht |
| Test | Molecule | Bei Push/PR | Testergebnisse |
| Testlauf | ansible-playbook --check | Bei Merge auf main | Diff-Ausgabe |
| Deploy Staging | {Controller/direkt} | Bei Merge auf main | Lauf-Log |
| Deploy Prod | {Controller/direkt} | Manuelle Freigabe | Lauf-Log |
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 · 163 lines · 8 tokens per session scan A e9620cddb455
deploy-setup is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 1,385 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
deploy
Deploy application with pre/post-deploy checks.
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn subagents to interact with Nx Cloud, run deterministic decision scripts, and take action based on the results.
security-scan
Run security audit on codebase.
implement
You are in full autonomous implementation mode. Follow the VisionAgent agentic task approach from CLAUDE.md rigorously.
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.