Awesome DevOps is a curated directory of platforms, tools, practices, and learning resources for DevOps, the combination of development and operations methods used to deliver and run software. It helps organizations and site reliability engineering teams find resources for building, improving, and operating software delivery practices.
Borrowing it
Nothing to install: this file belongs to wmariuss/awesome-devops. 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/wmariuss/awesome-devops/main/.github/instructions/website.instructions.mdgit clone --depth 1 https://github.com/wmariuss/awesome-devopsWrote 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/wmariuss/awesome-devops/website)<a href="https://agentmods.dev/instructions/wmariuss/awesome-devops/website"><img src="https://agentmods.dev/badge/instructions/wmariuss/awesome-devops/website/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/wmariuss/awesome-devops/website"><img src="https://agentmods.dev/badge/instructions/wmariuss/awesome-devops/website.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.00262 | $0.00262 |
| Opus 5.5 | $0.00105 | $0.00105 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
awesome-devops website.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 24d 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.
What it actually says
Reviewing the website
The website is an Astro static site built from README.md. See website/README.md.
- README.md stays the source of truth. Flag code that hardcodes tools, categories or descriptions that belong in README.md.
- Data the browser needs is passed as props from
src/lib/site.mjs. Code insrc/components/*.tsxruns in the browser: it must not importnode:modules orsrc/lib/site.mjs(usesrc/lib/format.mjs). - Colours, type and spacing come from the tokens at the top of
src/styles/global.css. Flag new hard-coded colours or fonts outside the tokens. - Every page must work at 390px wide: no horizontal page scroll, controls reachable, text not clipped.
- Interactive elements must be real links or buttons, keyboard-reachable, with visible focus. Links that open a new tab use
rel="noopener". - Never read secrets or call paid APIs from site code. The only scripts that call external APIs are in
website/scripts/and run in CI. - Changes to
website/scripts/review/change how pull requests are reviewed: check that pull request content is still only read as data and never executed.
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.
- 24d ago First seen · 16 lines · 262 tokens per session scan A 106bb9f3eaee
awesome-devops website.instructions.md is an instructions file published in the GitHub repository wmariuss/awesome-devops (4,441 stars, last pushed yesterday), licensed CC0-1.0. It adds 262 tokens to every session, about $0.0010 per session on Opus 5.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-10-05.
Other instructions, from other repositories
awesome-ai-rules copilot-instructions.md
Copilot instructions for shumatsumonobu/awesome-ai-rules, covering copilot instructions, code style, database and don't.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).