Borrowing it
Nothing to install: this file belongs to andyrids/icm-spec. 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/andyrids/icm-spec/main/AGENTS.mdgit clone --depth 1 https://github.com/andyrids/icm-specWrote 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/andyrids/icm-spec/agents-md)<a href="https://agentmods.dev/instructions/andyrids/icm-spec/agents-md"><img src="https://agentmods.dev/badge/instructions/andyrids/icm-spec/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/andyrids/icm-spec/agents-md"><img src="https://agentmods.dev/badge/instructions/andyrids/icm-spec/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.00830 | $0.00830 |
| Opus 5.5 | $0.00332 | $0.00332 |
| Sonnet 5.5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
icm-spec 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 2mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
icm-spec plugin
This project contains a plugin for implementing spec-driven development alongside Interpretable Context Methodology (ICM).
ICM orchestrates agent workflows through workspaces with folder structure, markdown and scripts.
Workspaces use dedicated pipelines containing stages with a specific input, process and output. Conditional and unconditional review gates MUST be respected to allow human inspection and feedback loops.
Context hierarchy
Five layers. Layers 0 to 2 route; layers 3 and 4 carry content. Load a layer only when the work has reached it - reading ahead is how a stage acquires context it was designed not to have.
| Layer | Role | Path | immutable |
Budget |
|---|---|---|---|---|
| 0 | Global identity | AGENTS.md |
false | 900 |
| 1 | Workspace routing | CONTEXT.md |
false | 300 |
| 2 | Stage routing | ICM/*/CONTEXT.md |
false | 500 |
| 2 | Stage contract | ICM/*/stages/**/CONTEXT.md |
false | 500 |
| 3 | Reference material | ICM/_config/reference-*.md, both READMEs |
true | 2500 |
| 3 | Reference material | specs/**/*.md |
false | - |
| 4 | Working artifact | plans/*.md |
false | - |
| 4 | Working artifact | ICM/*/stages/**/output/*.md |
false | - |
Frontmatter
Every file above carries context-hierarchy, context-hierarchy-role and immutable as tabled,
plus recommended-context-tokens where a target is given. Beyond those:
- Budgets are a signal, not an enforced limit. A file that outgrows one is worth a look - it may have started doing another layer's job. Specs are unbudgeted - a spec is as long as the behaviour it declares.
- Layer 3 carries
tags: [keyword, ...].immutable: truemarks the factory configuration, amended deliberately, not in passing. Specs are not part of it: the pipeline exists to amend them, and stage 01 owns every change. plans/*.mdcarriesstatus-planned | in-progress | done | blocked | cancelled- plus the query fieldsdepends,specs,authors,issuesandpr, contracted inplans/README.md. Every coverage and ripple check reads them.ICM/*/stages/**/output/*.mdcarriesstatus: in-progress | in-review | done. It is ephemeral scratch, gitignored.
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.
- 2mo ago First seen · 65 lines · 830 tokens per session scan A 2e91889f03e0
icm-spec AGENTS.md is an instructions file published in the GitHub repository andyrids/icm-spec (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 830 tokens to every session, about $0.0033 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-08-31.
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.