What is ai-instructions ansible-config.instructions.md?

A set of rules for writing Ansible configuration files, which control how Ansible runs automation tasks on computers.

Use it when creating or reviewing ansible.cfg files and related execution settings.

It keeps configuration files consistent and makes inventory, SSH behavior, caching, and timing easier to manage.

How lsampaioweb/ai-instructions configures GitHub Copilot

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.github/instructions/ansible-config.instructions.md

Clone the repo

git clone --depth 1 https://github.com/lsampaioweb/ai-instructions

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/ansible-config/github.svg)](https://agentmods.dev/instructions/lsampaioweb/ai-instructions/ansible-config)

Your own site

<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/ansible-config"><img src="https://agentmods.dev/badge/instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/ansible-config"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/ansible-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 611 This file is loaded in full into every session.

When invoked 611 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00611	$0.00611
Opus 5	$0.00305	$0.00305
Sonnet 5	$0.00122	$0.00122
Haiku 4.5	$0.00061	$0.00061

Measured 5d ago against content hash 0447f8c82dd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ai-instructions ansible-config.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 5d 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.

.github/instructions/ansible-config.instructions.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 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 inventory set to the repository-managed inventory path (for example inventory/hosts or inventory/home).
Always set forks explicitly.
Always set retry_files_enabled = false.
Set gathering = smart as the global default for SSH-based projects.
Set gather_facts: false at the play level when a play requires no facts instead of modifying the global gathering setting.

Callbacks and profiling

Set callbacks_enabled = timer, profile_roles as the baseline for all projects.
Add project-specific plugins to callbacks_enabled only when the plugin provides observability or profiling value specific to your playbook domain (for example, profile_tasks for task-level timing diagnostics).

Fact caching

Set fact_caching, fact_caching_connection, and fact_caching_timeout explicitly when the project benefits from caching.
Omit fact-caching directives (fact_caching, fact_caching_connection, fact_caching_timeout) when playbooks make no use of ansible_facts lookups or role-level facts.

SSH connection

Set pipelining = true when privilege escalation does not conflict with requiretty.
Set timeout explicitly.
Set ssh_args with ControlMaster=auto and ControlPersist.
Choose a ControlPersist duration proportional to the longest expected task gap.
Keep host_key_checking enabled by default.

Linting configuration

Maintain .ansible-lint at the project root with explicit skip_list and warn_list entries for project-specific exceptions.
Optionally override root .ansible-lint in roles/common/.ansible-lint or other specific roles when they have unique linting requirements (for example, roles with deprecated modules in files/ or special template conventions).
When a role does not have its own .ansible-lint, it inherits the root project configuration during ansible-lint runs.
Document any role-specific lint suppressions with # noqa: <rule> comments directly in the affected code.

Read the full file on GitHub · 52 lines

Changes

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.

5d ago First seen · 52 lines · 611 tokens per session scan A 0447f8c82dd0

Subscribe to this mod's changes

ai-instructions ansible-config.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 16d ago), licensed MIT. It adds 611 tokens to every session, about $0.0031 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.

DevOps and cloud

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

ai-instructions: Instructions file for GitHub Copilot