Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.github/instructions/ansible-architecture.instructions.mdgit 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/instructions/lsampaioweb/ai-instructions/ansible-architecture)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/ansible-architecture"><img src="https://agentmods.dev/badge/instructions/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/instructions/lsampaioweb/ai-instructions/ansible-architecture"><img src="https://agentmods.dev/badge/instructions/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.00503 | $0.00503 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
ai-instructions ansible-architecture.instructions.md 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 6d 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 — 45 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.instructions.md. - For role structure and variable-boundary rules, defer to
ansible-role.instructions.md. - For
ansible.cfgruntime defaults and SSH settings, defer toansible-config.instructions.md.
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.instructions.md.
Safety Guards
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.
- 6d ago First seen · 45 lines · 503 tokens per session scan A 31859bc06f35
ai-instructions ansible-architecture.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 17d ago), licensed MIT. It adds 503 tokens to every session, about $0.0025 per session on Opus 5. 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-09-03.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.