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/sibilleb/AAP-Enterprise-MCP-ServerWrote 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/sibilleb/aap-enterprise-mcp-server/ansible)<a href="https://agentmods.dev/rules/sibilleb/aap-enterprise-mcp-server/ansible"><img src="https://agentmods.dev/badge/rules/sibilleb/aap-enterprise-mcp-server/ansible/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/sibilleb/aap-enterprise-mcp-server/ansible"><img src="https://agentmods.dev/badge/rules/sibilleb/aap-enterprise-mcp-server/ansible.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.07046 |
| Opus 5 | $0.00000 | $0.03523 |
| Sonnet 5 | $0.00000 | $0.01409 |
| Haiku 4.5 | $0.00000 | $0.00705 |
Grade A, and why
ansible 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 9d 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 — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Adopt and adhere to the following Ansible best practices to ensure maintainable, reusable, and efficient automation code. This guide provides standards for code organization, common patterns, performance optimization, security, testing, tooling, and common pitfalls to avoid.
1. Code Organization and Structure
- Structure your Ansible projects in a clear and consistent manner to enhance readability and maintainability.
1.1 Directory Structure Best Practices
- Root Directory:
ansible.cfg: Ansible configuration file. This should live in the root directory of your project.inventory/: Contains your inventory files (hosts, groups, and variables).hosts: Main inventory file.group_vars/: Directory for group-specific variables.all/: Contains variables that apply to all hosts.vars.yml: Primary file for common variables.vault.yml: Encrypted variables.
<group_name>/: Directory for variables specific to a group.vars.yml: Group-specific variables.vault.yml: Encrypted group variables.
host_vars/: Directory for host-specific variables.<host_name>/: Directory for a specific host.vars.yml: Host-specific variables.vault.yml: Encrypted host variables.
playbooks/: Directory for your Ansible playbooks.site.yml: Main playbook, orchestrating other playbooks.<environment>.yml: Playbooks tailored to different environments (e.g., staging.yml, production.yml).<component>.yml: Playbooks for specific components (e.g., webservers.yml, databases.yml).
roles/: Directory for reusable Ansible roles.<role_name>/:tasks/: Contains tasks for the role.main.yml: Entry point for the role's tasks.
handlers/: Contains handlers for the role.main.yml: Entry point for the role's handlers.
defaults/: Contains default variable values for the role.main.yml: Default variable values.
vars/: Contains role-specific variables.main.yml: Role-specific variables.
meta/: Contains metadata about the role.main.yml: Role metadata (e.g., dependencies, author).
templates/: Contains Jinja2 templates for the role.files/: Contains static files used by the role.
library/: (Optional) Custom Ansible modules.filter_plugins/: (Optional) Custom Jinja2 filter plugins.lookup_plugins/: (Optional) Custom lookup plugins.plugins/: All of the above (library, filter, lookup, etc) should be placed in respective subfolders in this directoryrequirements.yml: Lists roles to be downloaded from Ansible Galaxy.README.md: Project documentation.
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.
- 9d ago First seen · 553 lines · 7,046 tokens per session scan A a066f0cf0d1f
ansible is a cursor rule published in the GitHub repository sibilleb/AAP-Enterprise-MCP-Server (33 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,046 tokens. 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 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.