Borrowing it
Nothing to install: this file belongs to rshade/mcp-devtools-server. 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/rshade/mcp-devtools-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/rshade/mcp-devtools-serverWrote 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/rshade/mcp-devtools-server/claude-md)<a href="https://agentmods.dev/instructions/rshade/mcp-devtools-server/claude-md"><img src="https://agentmods.dev/badge/instructions/rshade/mcp-devtools-server/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/rshade/mcp-devtools-server/claude-md"><img src="https://agentmods.dev/badge/instructions/rshade/mcp-devtools-server/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.09702 | $0.09702 |
| Opus 5.5 | $0.03881 | $0.03881 |
| Sonnet 5.5 | $0.01940 | $0.01940 |
| Haiku 4.5 | $0.00970 | $0.00970 |
Grade A, and why
mcp-devtools-server 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 1mo 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 — 1,240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is an MCP (Model Context Protocol) DevTools server project built with Node.js/TypeScript. The server provides standardized development tool integration for AI assistants.
Current Work: See GitHub Issues and Milestones for active development priorities.
Specialized Agents Available
This project has custom agents in .claude/ for common tasks. Use these instead of implementing manually:
Implementation Agents
/implement-python-tool [issue-number]
- Implements Python tools from Epic #131
- Follows Go tools pattern with cache optimization
- Enforces 85-90%+ test coverage
- Runs all quality gates
/quick-fix [issue-number]
- Fast bug fixes (<1 hour, <50 lines)
- Best for linting errors, test failures, docs
- Rejects complex issues
Issue Management
/triage-issues [filter]
- Categorizes and labels issues using
gh issue list/view/edit - Assigns priorities (P0-P3)
- Detects duplicates and stale issues
- Filters: all, unlabeled, stale, P1
Code Review
/review-pr [pr-number] [--fix]
- Deep review across 5 dimensions (correctness, security, performance, maintainability, best practices)
- Uses
gh pr view/diff/checks - Optional: implements fixes with --fix flag
- Enforces quality gates
When to use agents:
- ✅ Implementing Python tools (issues #132-144)
- ✅ Quick bug fixes
- ✅ Issue triage before sprint planning
- ✅ Comprehensive PR reviews
See .claude/README.md for complete documentation.
Build and Test Commands
You can use either make commands (recommended) or npm scripts directly.
Makefile is a thin wrapper around npm - npm is the source of truth.
# View all available commands
make help
# Common commands
make install # Install dependencies
make build # Build TypeScript
make dev # Start development server
make test # Run tests
make lint # Run all linters (TypeScript, Markdown, YAML)
make check # Run all linters and tests
make all # Complete CI pipeline (install, check, build)
# Or use npm scripts directly
npm install
npm run build
npm run dev
npm run lint
npm run lint:md
npm run lint:yaml
npm test
npm run clean
# Run single test file
npm test -- src/__tests__/tools/make-tools.test.ts
# Run tests matching a pattern
npm test -- --testNamePattern="make_lint"
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.
- 1mo ago First seen · 1,240 lines · 9,702 tokens per session scan A 0c697058247a
mcp-devtools-server CLAUDE.md is an instructions file published in the GitHub repository rshade/mcp-devtools-server (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 9,702 tokens to every session, about $0.0388 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-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).
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.