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-architecture)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/ansible-architecture"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/ansible-architecture/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-architecture"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/ansible-architecture.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.00525 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
ansible-architecture 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Architecture Baseline
Dependencies
- For task-execution conventions (task key order, idempotency, and module declarations), defer to
ansible-playbook-style.mdc. - For role structure and variable-boundary rules, defer to
ansible-role.mdc. - For
ansible.cfgruntime defaults and SSH settings, defer toansible-config.mdc.
Rules
Project layout
- When all layered instruction files are active simultaneously, each file's rules govern its own file-type scope.
- Apply task-level style rules at the
.ymlfile scope, not the project scope. - Keep orchestration entry points as top-level playbooks directly under the
ansible/root. - Keep implementation logic inside roles under
ansible/roles/. - Keep execution order explicit by using numbered top-level playbook filenames when sequencing matters.
- Keep inventory and group variable ownership inside
ansible/inventory/andansible/group_vars/. - Keep a shared
commonrole for reusable OS-specific utilities. - Import
commonrole utilities viatasks_from. - Store environment-specific values in
group_varsor rolevarsfiles.
Playbook declarations
- Keep each top-level playbook focused on a single concern (provisioning, updating, hardening, backup, restore).
- Compose multi-step pipelines from separate playbooks via
ansible.builtin.import_playbookin asite.yml.
Idempotency
- Keep playbooks idempotent so re-runs converge without unintended changes.
- Keep every play result deterministic: tasks must reach
okorskippedon a second run with nochangedstate on the target.
Validation & Tooling
- Validate YAML syntax on all playbooks and roles before committing.
- Document all ansible-core and ansible-lint versions used in CI/CD or development setup to ensure consistent validation across environments.
- For lint governance, ansible-lint configuration, and skip/warn list policy, see
ansible-config.mdc.
Safety Guards
- Never substitute role-based task composition with ad-hoc shell script files.
- Never introduce host-destructive operations without an explicit user request.
- Never hardcode environment-specific values in playbook files.
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 · 46 lines · 0 tokens per session scan A 993a860d57d2
ansible-architecture 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 525 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.