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/gitmaxd/context-repo-mcp/agents-mdgit clone --depth 1 https://github.com/Gitmaxd/context-repo-mcpWhat 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.00603 | $0.00603 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
context-repo-mcp AGENTS.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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<coding_guidelines>
context-repo-mcp
This package is the official network-dependent stdio bridge to the hosted
Context Repo MCP at https://contextrepo.com/mcp.
Architecture
stdio MCP client
-> src/index.js
-> src/bridge.js
-> https://contextrepo.com/mcp
src/config.jsresolves and validates environment configuration.src/index.jsframes newline-delimited stdin, dispatches concurrently, and writes JSON-RPC responses to stdout.src/bridge.jsperforms one opaque HTTP POST and classifies the response.
The hosted MCP is the only owner of tools, prompts, resources, schemas, business errors, and output shapes. Do not add local registrations, REST dispatch, formatters, or Context Repo business behavior.
Build and test
npm install
npm test
npm ls --all
npm pack --dry-run
- Package manager: npm
- Runtime: Node.js 18 or later
- Modules: ES modules
- Tests: built-in
node:test - Dependencies: none
Tests must use injected fetch or loopback servers bound to 127.0.0.1.
Automated tests must not call contextrepo.com or require a real API key.
Transport invariants
- Send the exact input line as the HTTP body.
- Relay valid hosted JSON-RPC text without parsing and reserializing it.
- Preserve
content,structuredContent,_meta, and unknown fields. - Append only the terminating LF on stdout.
- Keep stdout JSON-only; diagnostics belong on stderr.
- Never log keys, authorization headers, request bodies, response bodies, stack traces, filesystem paths, or raw network errors.
- Do not retry POST requests.
- Use
redirect: "error"and the 30-second abort timeout. - Treat SSE, multiline JSON, malformed JSON, and non-JSON responses as failures. Do not add an SSE parser.
Configuration
CONTEXTREPO_API_KEY: canonical API key.CONTEXT_REPO_API_KEY: deprecated compatibility alias.CONTEXTREPO_MCP_URL: development/test MCP endpoint override.- Default endpoint:
https://contextrepo.com/mcp.
The npm bridge does not implement OAuth. OAuth-capable clients should connect directly to the hosted endpoint.
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.
- 2d ago First seen · 78 lines · 603 tokens per session scan A 8986d163dde6
context-repo-mcp AGENTS.md is an instructions file published in the GitHub repository Gitmaxd/context-repo-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 603 tokens to every session, about $0.0030 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.