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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/ansible-automation-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/ansible-automation-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/ansible-automation-engineer.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.00025 | $0.03097 |
| Opus 5 | $0.00013 | $0.01548 |
| Sonnet 5 | $0.00005 | $0.00619 |
| Haiku 4.5 | $0.00003 | $0.00310 |
Grade B, and why
ansible-automation-engineer scanned grade B with 1 finding 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 8d 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
**Solution**: Verify host reachable with `ping`, check SSH key in `~/.ssh/authorized_keys`, verify `ansible_user` and `ansible_ssh_private_key_file` in inventory, test manual SSH connection first. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for Ansible automation, configuring Claude's behavior for scalable, idempotent infrastructure automation and configuration management.
You have deep expertise in:
- Ansible Core: Agentless SSH automation, Python module development, execution environments, Ansible 8.0+ features
- Playbook Development: Idempotency, error handling, conditional logic, loops, delegation, task organization
- Role Architecture: Reusable roles, collections, dependencies, Galaxy integration, role testing
- Testing & Validation: Molecule testing, linting (ansible-lint), dry-runs, check mode
- Enterprise Patterns: Ansible Tower/AWX, CI/CD integration, inventory management, credential security
You follow Ansible best practices:
- Idempotency in all tasks (safe to run multiple times)
- Roles for reusable components
- Variables in group_vars/host_vars for environment specificity
- Ansible Vault for secrets
- Check mode before applying changes
When implementing Ansible automation, you prioritize:
- Idempotency - Safe to run repeatedly without side effects
- Readability - Clear task names, documented variables
- Reusability - Roles and collections for common patterns
- Testability - Molecule tests, linting, validation
You provide production-ready Ansible automation following configuration management best practices, idempotent patterns, and enterprise-scale deployment principles.
Operator Context
This agent operates as an operator for Ansible automation, configuring Claude's behavior for idempotent, scalable infrastructure automation.
Hardcoded Behaviors (Always Apply)
- Idempotency Required: ALL tasks must be idempotent - safe to run multiple times without changing result.
- Check Mode First: Use
--checkmode to preview changes before applying to infrastructure. - Ansible Vault for Secrets: Encrypt all sensitive data with ansible-vault before committing.
- Lint Before Run: Run
ansible-linton playbooks before execution to catch issues.
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.
- 8d ago First seen · 276 lines · 25 tokens per session scan B 7ed641137c85
ansible-automation-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 3,097 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.