Interpretable Context Methodology is a way to build agent workflows from numbered folders and Markdown files, with each file providing the prompts and context for one stage. It is for sequential tasks where a single AI agent follows a filesystem-defined process and people may review each stage. The catalogue skills support workflows built with this approach.
Borrowing it
Nothing to install: this file belongs to RinDig/Interpretable-Context-Methodology. 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/RinDig/Interpretable-Context-Methodology/main/CLAUDE.mdgit clone --depth 1 https://github.com/RinDig/Interpretable-Context-MethodologyWrote 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/rindig/interpretable-context-methodology/claude-md)<a href="https://agentmods.dev/instructions/rindig/interpretable-context-methodology/claude-md"><img src="https://agentmods.dev/badge/instructions/rindig/interpretable-context-methodology/claude-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/rindig/interpretable-context-methodology/claude-md"><img src="https://agentmods.dev/badge/instructions/rindig/interpretable-context-methodology/claude-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.00439 | $0.00439 |
| Opus 5.5 | $0.00176 | $0.00176 |
| Sonnet 5.5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
Interpretable-Context-Methodology 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 1mo 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
Interpreted-Context-Methdology
ICM is a framework for building structured, multi-stage AI workflows out of markdown files and folder conventions. Each workspace gives AI agents the right context at each stage of a task, and gives humans clear edit surfaces between stages.
Folder Map
model-workspace-protocol/
├── CLAUDE.md (you are here)
├── README.md (project overview)
├── LICENSE
├── _core/ (shared conventions and templates)
│ ├── CONVENTIONS.md (source of truth for all patterns)
│ ├── placeholder-syntax.md (how {{VARIABLES}} work)
│ └── templates/ (blank starting points for new workspaces)
└── workspaces/
├── script-to-animation/ (content idea -> animated video)
├── course-deck-production/ (unstructured material -> course PowerPoints)
└── workspace-builder/ (builds new MWP workspaces)
Routing
| You want to... | Go to |
|---|---|
| Create content with script-to-animation | workspaces/script-to-animation/CLAUDE.md |
| Build course slide decks from source material | workspaces/course-deck-production/CLAUDE.md |
| Build a new workspace for any domain | workspaces/workspace-builder/CLAUDE.md |
| Read the full MWP specification | _core/CONVENTIONS.md |
| Understand the placeholder system | _core/placeholder-syntax.md |
| Use a template for a new workspace | _core/templates/ |
Triggers
| Keyword | Action |
|---|---|
setup |
Run onboarding in whatever workspace you are in |
status |
Show pipeline completion for the current workspace |
How It Works
Each workspace is self-contained with its own CLAUDE.md. Navigate into a workspace folder and that workspace's CLAUDE.md takes over. You do not need to read this root file once you are inside a workspace.
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.
- 1mo ago First seen · 43 lines · 439 tokens per session scan A 9c297539a88c
Interpretable-Context-Methodology CLAUDE.md is an instructions file published in the GitHub repository RinDig/Interpretable-Context-Methodology (1,377 stars, last pushed 18d ago), licensed MIT. It adds 439 tokens to every session, about $0.0018 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-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).
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.