Borrowing it
Nothing to install: this file belongs to claude-did-this/MCPControl. 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/claude-did-this/MCPControl/main/CLAUDE.mdgit clone --depth 1 https://github.com/claude-did-this/MCPControlWrote 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/claude-did-this/mcpcontrol/claude-md)<a href="https://agentmods.dev/instructions/claude-did-this/mcpcontrol/claude-md"><img src="https://agentmods.dev/badge/instructions/claude-did-this/mcpcontrol/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.1 | $0.00566 | $0.00566 |
| Opus 5 | $0.00283 | $0.00283 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
MCPControl 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 7d 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
MCPControl - Development Guide
Build & Test Commands
- Build:
pwsh.exe -c "npm run build"- Compiles TypeScript to JavaScript - Lint:
pwsh.exe -c "npm run lint"- Runs ESLint to check code quality (TS and JS) - Format:
pwsh.exe -c "npm run format"- Runs Prettier to format code - Format Check:
pwsh.exe -c "npm run format:check"- Checks if files are properly formatted - Test:
pwsh.exe -c "npm run test"- Runs all Vitest tests - Run single test:
pwsh.exe -c "npm run test -- tools/keyboard.test.ts"orpwsh.exe -c "npm run test -- -t \"specific test name\"" - Watch tests:
pwsh.exe -c "npm run test:watch"- Runs tests in watch mode - Coverage:
pwsh.exe -c "npm run test:coverage"- Generates test coverage report - E2E Test:
cd test && ./e2e-test.sh [iterations]- Runs end-to-end tests with Claude and MCPControl
Running with HTTPS/TLS
MCPControl supports HTTPS for secure SSE connections (mandatory per MCP spec for production):
node build/index.js --sse --https --cert /path/to/cert.pem --key /path/to/key.pem- Default HTTPS port is still 3232 (use --port to change)
- Both --cert and --key are required when using --https
Note: MCP Servers are typically launched by the Client as a subprocess.
Code Style Guidelines
- Imports: Use ES module syntax with named imports
- Types: Define TypeScript interfaces for inputs/outputs in
types/directory - Error Handling: Use try/catch with standardized response objects
- Naming: camelCase for variables/functions, PascalCase for interfaces
- Functions: Keep functions small and focused on single responsibility
- Comments: Add JSDoc comments for public APIs
- Testing:
- Unit tests: Place in same directory as implementation with
.test.tssuffix - E2E tests: Added to the
test/directory
- Unit tests: Place in same directory as implementation with
- Formatting: Code is formatted using Prettier (pre-commit hooks will run automatically)
- Error Responses: Return
{ success: false, message: string }for errors - Success Responses: Return
{ success: true, data?: any }for success - Linting: Both TypeScript and JavaScript files are linted with ESLint
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.
- 7d ago First seen · 35 lines · 566 tokens per session scan A 02bc2344ba6a
MCPControl CLAUDE.md is an instructions file published in the GitHub repository claude-did-this/MCPControl (329 stars, last pushed 9mo ago), licensed MIT. It adds 566 tokens to every session, about $0.0028 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-30.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.