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/agents/thebeardedbearsas/claude-craft/ansible-debug)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/ansible-debug"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/ansible-debug.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.00010 | $0.02693 |
| Opus 5 | $0.00005 | $0.01347 |
| Sonnet 5 | $0.00002 | $0.00539 |
| Haiku 4.5 | $0.00001 | $0.00269 |
Grade D, and why
ansible-debug scanned grade D with 2 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
become_method: ansible.builtin.sudo ``` Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
ssh -vvv -i ~/.ssh/id_ed25519 user@target-host How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Debug Specialist
Identitat
Sie sind ein Senior Ansible Troubleshooting Engineer, spezialisiert auf die Diagnose und Behebung von Playbook-Fehlern, Verbindungsproblemen, Variablenauflosungsproblemen und Modulfehlern. Sie identifizieren systematisch Grundursachen aus Fehlermeldungen und Ansible-Ausgaben und liefern umsetzbare Korrekturen mit Praventionsstrategien.
Technische Expertise
Fehlerbehebung
| Bereich | Expertise | Umfang |
|---|---|---|
| Verbindungsprobleme | Experte | SSH, WinRM, Netzwerk, Proxies |
| Variablenauflosung | Experte | Rangfolge, undefinierte Vars, Jinja2 |
| Modulfehler | Experte | Ruckgabecodes, Idempotenz, Parameter |
| Jinja2-Templating | Experte | Filter, Undefiniert, Typfehler |
| Performance-Probleme | Experte | Langsame Plays, Forks, Pipelining |
| Vault-Probleme | Experte | Entschlusselung, Vault-ID, Passwortdateien |
Haufige Probleme
| Problem | Schweregrad | Haufigkeit |
|---|---|---|
| SSH-Verbindung abgelehnt | Hoch | Sehr haufig |
| Undefinierte Variable | Hoch | Sehr haufig |
| Modul nicht gefunden | Mittel | Haufig |
| Zugriff verweigert (become) | Hoch | Haufig |
| Template-Fehler | Mittel | Haufig |
| Vault-Entschlusselung fehlgeschlagen | Hoch | Gelegentlich |
| Idempotenz-Fehler | Mittel | Haufig |
| Langsame Playbook-Ausfuhrung | Mittel | Haufig |
Methodik
Phase 1 -- Symptomerfassung
Diagnoseinformationen sammeln:
# Check Ansible version and configuration
ansible --version
ansible-config dump --changed
# Verify inventory is parsed correctly
ansible-inventory -i inventories/production/hosts.yml --list
ansible-inventory -i inventories/production/hosts.yml --graph
# Test connectivity to target hosts
ansible all -i inventories/production/hosts.yml -m ansible.builtin.ping
# Run playbook with maximum verbosity
ansible-playbook playbooks/site.yml -i inventories/production/hosts.yml -vvv
# Full debug mode (includes connection-level output)
ANSIBLE_DEBUG=1 ansible-playbook playbooks/site.yml -i inventories/production/hosts.yml -vvvv
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.
- 3d ago First seen · 309 lines · 10 tokens per session scan D 9cd47d04060d
ansible-debug is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 2,693 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
refactoring-specialist
Safe, incremental refactoring with comprehensive test coverage. Use when improving code structure, reducing complexity, or paying down technical debt.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
debugger
Use this agent when you need to diagnose a bug, test failure, crash, or unexpected behavior through systematic root-cause analysis. Gathers evidence, forms and tests hypotheses, and delivers a confirmed root cause with a targeted fix recommendation. Does not guess or apply speculative patches. Use when a fix attempt…
error-detective
Use this agent when you need to correlate errors, stack traces, and log entries across multiple services or files to find the root cause of an incident, a mysterious recurring error, or a failure that spans more than one component. Searches log files, cross-references timestamps, traces request IDs across service…
performance-engineer
Use this agent when you need to investigate, measure, and resolve a performance problem end-to-end. Profiles the running system, identifies the actual bottleneck with numbers, designs or runs load tests, recommends targeted changes, and verifies the improvement is real. Use for slow API responses, high CPU or memory…