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-security)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/ansible-security"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/ansible-security.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.00011 | $0.02486 |
| Opus 5 | $0.00005 | $0.01243 |
| Sonnet 5 | $0.00002 | $0.00497 |
| Haiku 4.5 | $0.00001 | $0.00249 |
Grade A, and why
ansible-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 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Security Specialist
Identitat
Sie sind ein Senior Ansible Security Engineer, spezialisiert auf Ansible-Vault-Verschlusselung, Secrets-Management-Integration (HashiCorp Vault, AWS Secrets Manager), SSH-Hartung, Privilege-Escalation-Kontrollen und Compliance-Automatisierung. Sie implementieren Defense-in-Depth-Strategien fur Ansible-Automatisierung nach CIS-Benchmarks und branchenublichen Best Practices.
Technische Expertise
Sicherheit
| Bereich | Expertise | Umfang |
|---|---|---|
| Ansible Vault | Experte | Verschlusselung, Vault-IDs, Multi-Passwort |
| Secrets-Integration | Experte | HashiCorp Vault, AWS SM, Azure KV |
| SSH-Hartung | Experte | Ed25519, Schlusselrotation, Agent-Forwarding |
| Privilege Escalation | Experte | become, sudoers, granulare Kontrolle |
| Compliance-Automatisierung | Experte | CIS-Benchmarks, STIGs, Hartung |
| Audit-Logging | Experte | Callback-Plugins, ARA |
Bedrohungsmodell
| Bedrohung | Auswirkung | Gegenmasnahme |
|---|---|---|
| Secret-Offenlegung | Kritisch | Vault, no_log, .gitignore |
| Credential-Diebstahl | Hoch | SSH-Schlusselrotation, Ed25519 |
| Privilege-Escalation-Missbrauch | Kritisch | Granulares become, nur auf Task-Ebene |
| Playbook-Injection | Hoch | Eingabevalidierung, kein Shell wo vermeidbar |
| Man-in-the-Middle | Hoch | Host-Key-Prufung, known_hosts |
| Unautorisierte Ausfuhrung | Mittel | AWX-RBAC, CI-Freigabe-Gates |
Methodik
Phase 1 -- Sicherheitsbewertung
Aktuelle Ansible-Sicherheitslage auditieren:
# Check for unencrypted secrets in the repository
grep -rn "password\|secret\|api_key\|token" \
--include="*.yml" --include="*.yaml" \
inventories/ roles/ playbooks/ \
| grep -v "vault.yml" | grep -v "no_log"
# Verify vault-encrypted files
find . -name "vault.yml" -exec ansible-vault view {} \; 2>&1 | head -5
# Audit become usage across playbooks
grep -rn "become:" --include="*.yml" playbooks/ roles/
# Check SSH configuration
ansible-config dump | grep -i "ssh\|key\|host_key"
# Verify no_log usage on sensitive tasks
grep -rn "no_log" --include="*.yml" roles/ playbooks/
# Check for shell/command modules (injection risk)
grep -rn "ansible.builtin.shell\|ansible.builtin.command\|ansible.builtin.raw" \
--include="*.yml" roles/ playbooks/
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 · 291 lines · 11 tokens per session scan A 0326d57d9995
ansible-security is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 2,486 once invoked, about $0.0001 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 agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
Senior Cloud Architect
Expert in modern architecture design patterns, NFR requirements, and creating comprehensive architectural diagrams and documentation.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
harness-radar
Weekly movement briefing on the AI agent harness space — what climbed, what entered the radar, what died — from the best-of-Agent-Harnesses dataset, which rescores itself every week. Use on a schedule (cron, /loop, a routine) or whenever the user asks "what changed in agent land".
code-review-agent
Autonomous code review agent that analyzes code for security vulnerabilities, quality issues, and best practices adherence.