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/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/ansible-config)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/ansible-config"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/ansible-config/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/lsampaioweb/ai-instructions/ansible-config"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/ansible-config.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.00617 |
| Opus 5.5 | $0.00000 | $0.00247 |
| Sonnet 5.5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
ansible-config 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 14d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Configuration Contract
Naming Conventions
- Place
[defaults]before[ssh_connection]. - Place any project-specific sections after the standard sections.
- Write
# <reason>comments on the line above the key they document. - Use backticks when referencing section names in prose:
`[defaults]`,`[ssh_connection]`.
Rules
General formatting
- Do not quote scalar values.
Inventory and execution
- Keep
inventoryset to the repository-managed inventory path (for exampleinventory/hostsorinventory/home). - Always set
forksexplicitly. - Always set
retry_files_enabled = false. - Set
gathering = smartas the global default for SSH-based projects. - Set
gather_facts: falseat the play level when a play requires no facts instead of modifying the globalgatheringsetting.
Callbacks and profiling
- Set
callbacks_enabled = timer, profile_rolesas the baseline for all projects. - Add project-specific plugins to
callbacks_enabledonly when the plugin provides observability or profiling value specific to your playbook domain (for example,profile_tasksfor task-level timing diagnostics).
Fact caching
- Set
fact_caching,fact_caching_connection, andfact_caching_timeoutexplicitly when the project benefits from caching. - Omit fact-caching directives (
fact_caching,fact_caching_connection,fact_caching_timeout) when playbooks make no use ofansible_factslookups or role-level facts.
SSH connection
- Set
pipelining = truewhen privilege escalation does not conflict with requiretty. - Set
timeoutexplicitly. - Set
ssh_argswithControlMaster=autoandControlPersist. - Choose a
ControlPersistduration proportional to the longest expected task gap. - Keep
host_key_checkingenabled by default.
Linting configuration
- Maintain
.ansible-lintat the project root with explicitskip_listandwarn_listentries for project-specific exceptions. - Optionally override root
.ansible-lintinroles/common/.ansible-lintor other specific roles when they have unique linting requirements (for example, roles with deprecated modules infiles/or special template conventions). - When a role does not have its own
.ansible-lint, it inherits the root project configuration duringansible-lintruns. - Document any role-specific lint suppressions with
# noqa: <rule>comments directly in the affected code.
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.
- 14d ago First seen · 53 lines · 0 tokens per session scan A 134150e84ad7
ansible-config is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 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-10-04.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.