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/igrechuhin/cortex/claude-mdgit clone --depth 1 https://github.com/igrechuhin/CortexWrote 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/igrechuhin/cortex/claude-md)<a href="https://agentmods.dev/instructions/igrechuhin/cortex/claude-md"><img src="https://agentmods.dev/badge/instructions/igrechuhin/cortex/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.00738 | $0.00738 |
| Opus 5 | $0.00369 | $0.00369 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
Cortex 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE
Guidance for Claude Code agents in this repository. See also AGENTS.md.
Use Cortex MCP (MANDATORY)
Cortex MCP server holds all project knowledge, rules, and workflows. Never duplicate that here — fetch from Cortex MCP.
Start of every non-trivial task:
- Call
session()for orientation (< 1000 tokens) - Read
cortex://contextfor project context - Read
cortex://rulesfor coding standards
Pattern: session() → read resources → work
Zero-arg tools: All MCP tools accept empty {} (some MCP client bridges strip args). Tools read defaults from session config or use fallbacks. See AGENTS.md for full tool/resource reference.
Fix path: Before fixing errors, test failures, or quality/type issues, read cortex://context and cortex://rules first.
Thinking: Use think(). Lightweight for quick deliberation; full mode with thought_number, total_thoughts, next_thought_needed for multi-step reasoning.
Rules and standards: Read cortex://rules — do not read .cortex/rules/ or .cortex/synapse/ directly. Use Pydantic BaseModel for tool parameters and structured dispatch data, not dict[str, Any].
Quality and tests: Zero-arg tools only: run_quality_gate(), run_docs_gate(), autofix(). Do not run language-specific formatters/linters/test runners directly.
Memory bank, plans, reviews: Use manage_file(), plan(), update_memory_bank() — do not edit .cortex/ files directly.
AI agents: For detailed workflows (commit, implement, fix-path, etc.), read Synapse prompts and rules via Cortex MCP instead of adding guidance to CLAUDE.md or AGENTS.md.
Session Discipline
Single-goal sessions:
- Confirm one primary goal early; keep work scoped to it.
- Defer unrelated issues to follow-up sessions.
- Split multiple unrelated in-progress fixes into separate scoped passes.
Execution continuity
Once you have enough information, continue without waiting for "ok, proceed".
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 · 60 lines · 738 tokens per session scan A 10f6c581833f
Cortex CLAUDE.md is an instructions file published in the GitHub repository igrechuhin/Cortex (3 stars, last pushed 3d ago), licensed MIT. It adds 738 tokens to every session, about $0.0037 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-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).
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.