Borrowing it
Nothing to install: this file belongs to slxca/opencontext. 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/slxca/opencontext/master/CLAUDE.mdgit clone --depth 1 https://github.com/slxca/opencontextWrote 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/slxca/opencontext/claude-md)<a href="https://agentmods.dev/instructions/slxca/opencontext/claude-md"><img src="https://agentmods.dev/badge/instructions/slxca/opencontext/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/slxca/opencontext/claude-md"><img src="https://agentmods.dev/badge/instructions/slxca/opencontext/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.00392 | $0.00392 |
| Opus 5.5 | $0.00157 | $0.00157 |
| Sonnet 5.5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
opencontext 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 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.
What it actually says
CRITICAL MEMORY SYSTEM: OpenContext Protocol
You have access to persistent project context via OpenContext MCP tools (.opencontext/). Adherence to this protocol is mandatory for consistency across sessions.
1. Mandatory Pre-Flight: Inspect Context
Before editing, refactoring, or generating code that affects:
- Architecture, module boundaries, or dependency graph
- Database schemas, migrations, or models
- API contracts, route handlers, or DTOs
- Authentication, authorization, or security rules
Action Required: Execute read_context FIRST to check existing conventions, past design decisions, and project rules. Do NOT assume architectural patterns without reading relevant context topics.
2. Post-Implementation: Persist Changes
Immediately after introducing, altering, or deprecating conventions, run the corresponding OpenContext tool:
- Save/Update (
save_context):- When: You add or change an architectural pattern, schema, shared utility rule, or tech stack decision.
- Format: Concise, topic-scoped Markdown summary.
- Lifecycle Frontmatter: When updating an existing convention, you MUST include YAML frontmatter:
--- status: active | superseded | deprecated supersedes: previous_topic_slug ---
- Deprecate vs. Delete (
delete_context):- Use
status: deprecatedorstatus: supersededin YAML frontmatter if historical context is valuable. - Call
delete_contextONLY when a topic is fully obsolete or entirely removed from the codebase.
- Use
3. Execution Rules
- Never skip: Do not bypass
read_contexton multi-file or cross-cutting tasks to save tokens. - Fail-safe: If unsure whether an architectural decision exists, invoke
read_contextbefore taking action.
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 · 36 lines · 392 tokens per session scan A 963483d74378
opencontext CLAUDE.md is an instructions file published in the GitHub repository slxca/opencontext (8 stars, last pushed 2mo ago), licensed MIT. It adds 392 tokens to every session, about $0.0016 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-04.
Other instructions, from other repositories
repobrain copilot-instructions.md
Copilot instructions for study8677/repobrain, covering github copilot bootstrap instructions and hard rule — query the repobrain hub first.
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).