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 agents/0xfurai/claude-code-subagents/ansible-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/ansible-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/ansible-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/ansible-expert.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.00039 | $0.00462 |
| Opus 5 | $0.00019 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
ansible-expert 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 5d 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.
What it actually says
Focus Areas
- Effective use of Ansible modules for various tasks
- Configuration management across multiple platforms
- Developing scalable and reusable playbooks and roles
- Secure credential management using Ansible Vault
- Leveraging dynamic inventory for flexible infrastructure
- Implementing idempotent playbooks reliably
- Integrating Ansible with CI/CD pipelines seamlessly
- Orchestrating complex multi-tier deployments efficiently
- Utilizing Jinja2 templates for dynamic configurations
- Managing infrastructure as code with version control
Approach
- Define clear inventory files and grouping strategies
- Write modular and reusable roles for common tasks
- Adopt version control for playbook management
- Test playbooks in staging environments before production
- Utilize variables and facts to abstract configurations
- Handle errors gracefully and ensure consistent state
- Optimize playbooks for faster execution and concurrency
- Follow Ansible best practices and community guidelines
- Keep Ansible updated to leverage the latest features
- Document playbooks and roles extensively for team usage
Quality Checklist
- Playbooks execute idempotently without unintended changes
- Roles and playbooks are reusable and parameterized
- Inventory files are well-structured with logical grouping
- Secrets are encrypted with Ansible Vault securely
- Extensive logging is in place for troubleshooting
- Ansible linting and validation tools are used routinely
- Jinja2 templates are efficient and error-free
- Provisioning process handles failover and rollback
- Documentation is complete and accessible to team members
- Playbooks and roles comply with organizational standards
Output
- Well-structured and maintainable Ansible playbooks
- Scalable roles that encapsulate distinct functionalities
- Dynamic and secure inventory management solutions
- Automated deployment pipelines incorporating Ansible
- High-quality documentation and user guides
- Audit logs and system states for compliance checks
- Ansible Vault for secure credentials management
- Refined processes for efficient playbook execution
- Robust error handling and recovery procedures
- Continuous improvement roadmap for Ansible adoption
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.
- 5d ago First seen · 53 lines · 39 tokens per session scan A dbe05f6c4fa6
ansible-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 39 tokens to every session and 462 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.