Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/arjunprabhulal/devops-skills/agents-mdgit clone --depth 1 https://github.com/arjunprabhulal/devops-skillsWrote 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/arjunprabhulal/devops-skills/agents-md)<a href="https://agentmods.dev/instructions/arjunprabhulal/devops-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/arjunprabhulal/devops-skills/agents-md.svg" alt="Measured on agentmods" 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 | $0.02168 | $0.02168 |
| Opus 5 | $0.01084 | $0.01084 |
| Sonnet 5 | $0.00434 | $0.00434 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
devops-skills AGENTS.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 3d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents (and humans) working in this repository: the required shape of a skill, the
workflow for changing one, and the reasoning behind both. README.md describes what the collection
contains and how to install it.
What this repo is
A collection of 88 DevOps Agent Skills across 15 categories. Each skill is a single
SKILL.md under skills/<category>/<skill-name>/, loaded on demand when a matching task appears.
The shape of every skill
- Frontmatter — exactly three keys:
name(must equal the folder name),description(one paragraph with concrete "Use this whenever…" triggers and "For X usesibling" cross-references), andlicense: MIT. - Intro — one or two paragraphs framing the core principle, ending in a single bold principle line.
- 5–6 numbered
## N. Imperative headingsections — each explains the why, may carry at most one or two code blocks or tables total, and ends with a concreteDone when:line. ## Report— closes by stating the key decisions and, explicitly, the honest remaining gap.
Rules
- One responsibility per skill. Cross-reference siblings by name instead of repeating them.
- Be opinionated and explain why. A rule without a reason is not memorable.
- Principles over vendors. Name tools to illustrate; never tie a skill to one product.
- No placeholders. Every skill must be complete and technically correct.
Before committing
Run the validator:
python3 scripts/check-skills.py
It checks frontmatter, name/folder match, description length and triggers, the presence of a
Report section and Done-when checkpoints, balanced code fences, eval files, reference links, that
.claude-plugin/plugin.json matches the skills on disk, and that the Antigravity .agents/skills/
layout is in sync. When you add a skill, add its path to plugin.json and to the README catalogue.
Two layouts, one source
The canonical skills live under skills/<category>/<skill>/ (the Claude Code plugin layout).
Google Antigravity discovers skills from a flat .agents/skills/<skill>/ layout, which is
generated from the canonical tree and not committed — .agents/ is gitignored. After
adding or editing any skill, regenerate it locally:
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.
- 3d ago First seen · 167 lines · 2,168 tokens per session scan A 82ce4576d186
devops-skills AGENTS.md is an instructions file published in the GitHub repository arjunprabhulal/devops-skills (2 stars, last pushed 9d ago), licensed MIT. It adds 2,168 tokens to every session, about $0.0108 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-31.
Other instructions, from other repositories
ai-mind AGENTS.md
AGENTS.md instructions for HWYD/ai-mind, covering agents, version spec workspace continuity (mandatory), 项目定位, 事实来源优先级 and 开始大改前先读什么.
vvvv-skills CLAUDE.md
Claude Code instructions for tebjan/vvvv-skills, covering vvvv gamma, when to patch vs code, core concepts, live environment and important conventions.
pi AGENTS.md
AGENTS.md instructions for counterposition/pi, covering agents.md, commands, pattern: pnpm --filter @counterposition/pi-web-search run, single test file and single test by name.
hyperskills CLAUDE.md
Instructions for hyperb1iss/hyperskills, a project described as: My collection of agent skills for a variety of tasks.
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).
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.