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/d-padmanabhan/agent-engineering-handbookWrote 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/rules/d-padmanabhan/agent-engineering-handbook/190-ansible)<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/190-ansible"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/190-ansible.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.00018 | $0.04185 |
| Opus 5 | $0.00009 | $0.02093 |
| Sonnet 5 | $0.00004 | $0.00837 |
| Haiku 4.5 | $0.00002 | $0.00419 |
Grade B, and why
190-ansible scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
become_method = sudo become_user = root Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- curl How it starts
The opening of the file, as written. The whole thing — 834 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Configuration Management Best Practices
Guiding Principles
- Idempotency: Playbooks should produce same result regardless of how many times executed
- Declarative: Describe desired state, not imperative steps
- Modularity: Use roles for reusability
- Version Control: Track all playbooks, roles, and inventories in Git
- Testing: Test playbooks before production deployment
Project Structure
Standard Layout
ansible/
ansible.cfg # Ansible configuration
inventory/
production/
hosts # Production inventory
group_vars/
all.yml
webservers.yml
staging/
hosts
group_vars/
all.yml
playbooks/
site.yml # Master playbook
webservers.yml
database.yml
deploy.yml
roles/
common/
tasks/
main.yml
handlers/
main.yml
templates/
files/
vars/
main.yml
defaults/
main.yml
meta/
main.yml
nginx/
postgresql/
app/
group_vars/
all.yml # Variables for all hosts
webservers.yml # Variables for webserver group
host_vars/
web1.acme.com.yml # Variables for specific host
vault/
secrets.yml # Encrypted secrets
Ansible Configuration
ansible.cfg
[defaults]
# Inventory
inventory = inventory/production/hosts
host_key_checking = False
# Roles
roles_path = roles
# Output
stdout_callback = yaml
bin_ansible_callbacks = True
# Performance
forks = 10
gathering = smart
fact_caching = jsonfile
fact_caching_connection = /tmp/ansible_facts
fact_caching_timeout = 86400
# SSH
remote_user = ansible
private_key_file = ~/.ssh/ansible_key
timeout = 30
# Privilege escalation
become = True
become_method = sudo
become_user = root
become_ask_pass = False
# Logging
log_path = /var/log/ansible.log
[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=60s
pipelining = True
control_path = /tmp/ansible-ssh-%%h-%%p-%%r
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 · 834 lines · 18 tokens per session scan B ed749894b134
190-ansible is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 4,185 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.