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/readme.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/readme)<a href="https://agentmods.dev/instructions/wmariuss/awesome-devops/readme"><img src="https://agentmods.dev/badge/instructions/wmariuss/awesome-devops/readme/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/readme"><img src="https://agentmods.dev/badge/instructions/wmariuss/awesome-devops/readme.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.01096 | $0.01096 |
| Opus 5.5 | $0.00438 | $0.00438 |
| Sonnet 5.5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
awesome-devops readme.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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing README.md entries
README.md is the awesome-devops list and the single source of the website. Review every added or changed entry line against these rules. Rules marked must block the merge; rules marked should are suggestions.
Entry format
Every entry is exactly one line:
- [Name](https://url) - What the tool does, in one sentence. `tag` `tag`
- The line must start with
- [, then the name in brackets, the link in parentheses,-, the description, then one or more tags in backticks. - Entries inside a group (for example "On-premises" under Continuous Integration & Delivery) are indented by two spaces.
- The name should use the project's own spelling:
Kubernetes,GitLab,etcd.
Link
- The link must be the project's official website, or its GitHub repository if it has no website.
- The link must not contain tracking parameters:
utm_*,ref=,source=,campaign=,fbclid,gclid. - The link should use
https://. - The link must not already appear elsewhere in README.md. The same tool may be listed in two sections only when it clearly serves both (for example an API gateway that is also a service mesh).
Description
- The description must say what the tool does, in one sentence, ending with a period.
- It must be neutral. Reject marketing language: "best", "blazing fast", "revolutionary", "world-class", "ultimate", "#1", "leading", "next-gen", "game-changing".
- It should start with a capital letter and stay under 200 characters.
- It must match what the project's own website or repository says the tool does.
Pricing tags
Tags go at the end of the line, each in backticks, from this set only:
| Tag | Use it when |
|---|---|
oss |
The source code is public under an OSI-approved open source license. |
free |
A free plan or free usage exists, but the tool is not open source. |
paid |
Paid plans, an enterprise edition or paid support exist. |
self-hosted |
It can be installed on your own servers without being open source. |
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 · 79 lines · 1,096 tokens per session scan A bda10be550eb
awesome-devops readme.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 1,096 tokens to every session, about $0.0044 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).