Borrowing it
Nothing to install: this file belongs to marcusquinn/aidevops. 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/marcusquinn/aidevops/main/AGENTS.mdgit clone --depth 1 https://github.com/marcusquinn/aidevopsWrote 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/marcusquinn/aidevops/agents-md)<a href="https://agentmods.dev/instructions/marcusquinn/aidevops/agents-md"><img src="https://agentmods.dev/badge/instructions/marcusquinn/aidevops/agents-md/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/marcusquinn/aidevops/agents-md"><img src="https://agentmods.dev/badge/instructions/marcusquinn/aidevops/agents-md.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.01043 | $0.01043 |
| Opus 5.5 | $0.00417 | $0.00417 |
| Sonnet 5.5 | $0.00209 | $0.00209 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
aidevops 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 23d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI DevOps Framework - Developer Guide
Quick Reference
- User Guide:
.agents/AGENTS.md(deployed to~/.aidevops/agents/) - Commands:
./setup.sh(deploy) |.agents/scripts/linters-local.sh(quality) |.agents/scripts/version-manager.sh release [major|minor|patch] - Config: Runtime-specific (see
.agents/AGENTS.md"Runtime References") - Quality:
.agents/AGENTS.md"Framework Rules"
File Structure: TODO.md (tasks), todo/ (plans, PRDs), .agents/ (agents, tools, services, workflows, scripts).
Before extending: Read .agents/aidevops/architecture.md (design patterns, conventions, extension guide) and .agents/aidevops/purpose.md (value, ownership, and decision criteria).
Two AGENTS.md Files
| File | Purpose | Audience |
|---|---|---|
~/Git/aidevops/AGENTS.md |
Development guide | Contributors |
~/Git/aidevops/.agents/AGENTS.md |
User guide | Users of aidevops |
The .agents/AGENTS.md is copied to ~/.aidevops/agents/AGENTS.md by setup.sh.
Development Lifecycle
See .agents/AGENTS.md "Operational Routines" for code-change routing and
.agents/AGENTS.md "Git Workflow" for the full lifecycle.
Completion self-check: see .agents/AGENTS.md "Framework Rules > Task and completion discipline".
Contributing
See .agents/aidevops/ (architecture, setup) and .agents/tools/ (agent/MCP authoring) for framework development guidance:
| File | Purpose |
|---|---|
.agents/tools/build-agent/build-agent.md |
Composing efficient agents |
.agents/tools/build-agent/agent-review.md |
Reviewing and improving agents |
.agents/tools/build-mcp/build-mcp.md |
MCP server development |
.agents/tools/mcp-toolkit/mcporter.md |
MCP runtime toolkit (discover, call, generate CLIs) |
.agents/aidevops/architecture.md |
Framework structure |
.agents/aidevops/setup.md |
AI guide to setup.sh |
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.
- 23d ago Changed · +4 lines · +94 tokens per session eafa159d65dc
- 1mo ago Changed · +20 tokens per session ac6b7928bfd4
- 1mo ago Changed · +33 tokens per session 7e53b7559e84
- 1mo ago First seen · 89 lines · 896 tokens per session scan A cd6cfd400710
aidevops AGENTS.md is an instructions file published in the GitHub repository marcusquinn/aidevops (420 stars, last pushed today), licensed MIT. It adds 1,043 tokens to every session, about $0.0042 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-09-03.
Other instructions, from other repositories
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.