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/ktncodes/icm-template/claude-mdgit clone --depth 1 https://github.com/ktnCodes/icm-templateWrote 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/ktncodes/icm-template/claude-md)<a href="https://agentmods.dev/instructions/ktncodes/icm-template/claude-md"><img src="https://agentmods.dev/badge/instructions/ktncodes/icm-template/claude-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.00444 | $0.00444 |
| Opus 5 | $0.00222 | $0.00222 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
icm-template CLAUDE.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.
What it actually says
ICM — Identity
Purpose
A skill-based distribution of the Interpretable Context Methodology for organizing AI workflows using folder structure.
Folder Map
icm-template/
├── SKILLS
│ ├── icm-scaffold
│ │ └── SKILL.md # The skill — generates ICM layers on any project
│ ├── icm-sync
│ │ └── SKILL.md # Maintenance — syncs IDENTITY.md and CONTEXT.md with disk
│ └── icm-context-scaffold
│ └── SKILL.md # Maintenance — generates missing CONTEXT.md files
├── docs
│ ├── methodology.md # Full ICM explanation (5 layers, 5 principles)
│ ├── best-practices.md # Writing effective stage contracts and _config/
│ ├── layer-reference.md # Quick reference for all 5 layers
│ ├── model-adapters.md # Per-tool setup (Claude, Cursor, Copilot, Windsurf)
│ └── Interpretable_Context_Methdology_.pdf # Original research paper
├── IDENTITY.md # Layer 0 — workspace map
├── CONTEXT.md # Layer 1 — task routing
├── CLAUDE.md # You are here
├── LICENSE # MIT
└── README.md # Project overview and quick start
Rules
- The SKILL.md files are the primary products. Everything else is supporting documentation.
icm-scaffoldgenerates ICM layers on the user's project.icm-syncandicm-context-scaffoldmaintain them over time.- The skills generate files on the user's project — they do not generate files in this repo.
- Docs are educational — they explain the methodology for humans who want to understand the why.
- Do not add Python tools, templates, or scaffolding scripts. The skills replace all of those.
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 · 44 lines · 444 tokens per session scan A 6fa0792c4e22
icm-template CLAUDE.md is an instructions file published in the GitHub repository ktnCodes/icm-template (51 stars, last pushed 4mo ago), licensed MIT. It adds 444 tokens to every session, about $0.0022 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-30.
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).
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.