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/bugg1n/cortex-mcp/claude-mdgit clone --depth 1 https://github.com/BUGG1N/cortex-mcpWrote 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/bugg1n/cortex-mcp/claude-md)<a href="https://agentmods.dev/instructions/bugg1n/cortex-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bugg1n/cortex-mcp/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.00949 | $0.00949 |
| Opus 5 | $0.00475 | $0.00475 |
| Sonnet 5 | $0.00190 | $0.00190 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
cortex-mcp 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CORTEX MCP — Session Protocol
Standalone MCP server. Scans repositories, accumulates knowledge, and exposes it to AI agents.
Identity
Local MCP server (stdio) that acts as portfolio memory for AI agents. Scans repos (local, public/private GitHub), generates structured knowledge (YAML/JSONL), and exposes tools, resources, and prompts via the Model Context Protocol.
Architecture
src/
├── cli.ts # Entry point — subcommands: init, add, scan, sync, sources, remove, serve
├── config.ts # Config resolution (flags → yaml → env → auto-detect)
├── server.ts # MCP Server wiring (stdio transport)
├── types.ts # TypeScript types (strict, zero any)
├── index.ts # Barrel export
├── engine/
│ ├── knowledge-engine.ts # Orchestrator — loads and queries data
│ ├── yaml-parser.ts # YAML/JSONL parser
│ ├── search-index.ts # MiniSearch full-text index
│ ├── graph-traversal.ts # BFS/DFS on the knowledge graph
│ ├── file-reader.ts # Repository file reader
│ └── file-watcher.ts # Hot-reload via chokidar
├── mcp/
│ ├── tools/index.ts # MCP tools (read + write)
│ ├── resources/index.ts # MCP resources
│ └── prompts/index.ts # MCP prompts
├── scanner/
│ ├── index.ts # Repository scanner
│ └── detectors/ # Stack auto-detection
│ ├── package-json.ts # Node.js / TypeScript
│ ├── python.ts # Python
│ ├── java.ts # Java (Maven, Gradle)
│ ├── dotnet.ts # .NET / C#
│ ├── go.ts # Go
│ ├── rust.ts # Rust
│ ├── infra.ts # Terraform, Kubernetes, Helm
│ ├── docker.ts # Docker
│ ├── ci.ts # CI/CD
│ └── git.ts # Git metadata
├── sources/
│ └── index.ts # Source manager
└── writer/
└── index.ts # Knowledge writer (YAML/JSONL)
Rules
- TypeScript strict, zero
any - Data 100% in-memory after startup — no external database
- Knowledge files: YAML + JSONL in a configurable directory
- MCP transport: stdio (JSON-RPC)
- File watcher: chokidar, debounce 500ms
- Search: MiniSearch with fuzzy prefix, boosted fields (name 3x, desc 2x, tags 1.5x)
- Tool results capped at MAX_ITEMS=10
- Scanner detectors run in parallel, results deduplicated
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 · 99 lines · 949 tokens per session scan A 4f247feff5c0
cortex-mcp CLAUDE.md is an instructions file published in the GitHub repository BUGG1N/cortex-mcp (6 stars, last pushed 5mo ago), licensed MIT. It adds 949 tokens to every session, about $0.0047 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.