Borrowing it
Nothing to install: this file belongs to konstruktoid/hardened-images. 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/konstruktoid/hardened-images/master/.github/instructions/ansible.instructions.mdgit clone --depth 1 https://github.com/konstruktoid/hardened-imagesWrote 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/konstruktoid/hardened-images/ansible)<a href="https://agentmods.dev/instructions/konstruktoid/hardened-images/ansible"><img src="https://agentmods.dev/badge/instructions/konstruktoid/hardened-images/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/instructions/konstruktoid/hardened-images/ansible"><img src="https://agentmods.dev/badge/instructions/konstruktoid/hardened-images/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.00577 | $0.00577 |
| Opus 5 | $0.00289 | $0.00289 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
hardened-images ansible.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 8d 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.
Enterprise Ansible Hardening Instructions
Apply these rules to config/local.yml, config/ansible.cfg, and any
provisioning templates that configure the konstruktoid.hardening collection.
Authoring priorities
- Module-first implementation; avoid
shell/commandunless no safe module exists. - Always use the fully-qualified collection name (FQCN, for example
ansible.builtin.git) for every module call. - Declarative, idempotent tasks with descriptive names.
- Double-quoted YAML strings.
- Pin
konstruktoid.hardeningto an explicit tagged version, never a floating branch. - The collection ships independent, single-purpose roles and no umbrella role.
Adding or removing a role in
config/local.ymlchanges the hardening scope, so treat it like flipping a hardening variable.
Conservative security handling
Treat these konstruktoid.hardening variables and domains as high sensitivity
and change conservatively:
- SSH (
sshd_*), sudo, PAM, and user/group management - audit/logging (
auditd_*) and systemd service behavior - mounts, sysctl/kernel tuning, firewall rules (the
ufwandfirewalldroles) - crypto policy, protocol hardening, and service exposure
Do not flip a hardening variable to a less restrictive value (e.g.
sshd_permit_root_login: true, auditd_apply_audit_rules: false), and do not
drop a role from the play, without an explicit request and a documented reason
in the commit/PR description.
Compliance-aware behavior
- Favor patterns aligned with CIS and STIG hardening intent and CMMC-oriented objectives.
- Improve auditability, traceability, and enforcement consistency.
- Reference exact benchmark/control IDs only when verified in repository context; otherwise cite likely control areas and rationale.
Review priorities
- Security regression or weakening of existing hardening intent
- Over-privileged execution (
become, root scope, broad permissions) - Non-idempotent logic or risky shell pipelines
- Missing explicit ownership/mode on managed files
- Operational reliability issues (unsafe restarts, brittle conditions)
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.
- 8d ago Changed · +3 lines · +41 tokens per session beeb029363e2
- 13d ago First seen · 50 lines · 536 tokens per session scan A 383a8466b581
hardened-images ansible.instructions.md is an instructions file published in the GitHub repository konstruktoid/hardened-images (90 stars, last pushed 5d ago), licensed Apache-2.0. It adds 577 tokens to every session, about $0.0029 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-08-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
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.
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).