mcp-debugger AGENTS.md

Repository instructions for a TypeScript debugging server and its related packages. The project is a monorepo, meaning one repository contains several connected packages, each with its own source code.

In plain words
What is it for?
Working on debugger adapters, building packages, running development mode, executing targeted tests, and running the full test suite.
Why use it?
They explain the package layout and the commands needed to install, build, develop, and test the whole project or selected parts.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/debugmcp/mcp-debugger/agents-md
Clone the repo
git clone --depth 1 https://github.com/debugmcp/mcp-debugger

Made for: Codex, OpenCode.

Per session 791 This file is loaded in full into every session.
When invoked 791 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00791 $0.00791
Opus 5 $0.00396 $0.00396
Sonnet 5 $0.00158 $0.00158
Haiku 4.5 $0.00079 $0.00079

Measured 2d ago against content hash 31594ba8c7f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-debugger 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.

AGENTS.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

  • src/ contains the TypeScript CLI and server core that power the Debug MCP runtime.
  • packages/ hosts workspace modules (@debugmcp/shared, adapter-mock, adapter-python, adapter-ruby, adapter-javascript, adapter-rust, adapter-go, adapter-java, adapter-dotnet, adapter-cpp, codelldb-common, mcp-debugger) with their own src/ trees.
  • tests/ is grouped by scope: core/, adapters/*/, e2e/, plus shared utilities in tests/test-utils/ and fixtures under tests/fixtures/.
  • docs/ covers design notes; examples/ hosts adapter recipes; scripts/ stores CI helpers.
  • Build artifacts land in dist/; recorded assets and Docker helpers live in assets/ and docker/.

Build, Test, and Development Commands

  • pnpm install sets up the monorepo (respect the generated pnpm-lock.yaml).
  • pnpm build compiles every package and emits the aggregated dist/index.js.
  • pnpm dev launches the TypeScript entry point via ts-node for quick feedback.
  • pnpm test performs a full build, ensures Docker images are ready, and runs Vitest across all suites.
  • Targeted runs: pnpm test:unit, pnpm test:integration, pnpm test:e2e, pnpm test:coverage.
  • pnpm lint applies the workspace-wide ESLint config; add :fix to auto-format when safe.

Coding Style & Naming Conventions

  • Source files use ES modules, TypeScript strict mode, and two-space indentation; prefer PascalCase for classes, camelCase for functions, and SCREAMING_SNAKE_CASE for constants.
  • Align new utilities with the patterns in src/utils/ (utility modules — mix of pure functions and service classes — with explicit exports).
  • ESLint (eslint.config.js) enforces TypeScript recommended rules, unused-variable patterns, and environment-specific overrides (e.g., relaxed rules for test files and mock utilities)—run it before opening a PR.
  • Avoid default exports; monorepo packages rely on named exports for tree shaking and test isolation.

Read the full file on GitHub · 35 lines

Changes

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.

  1. 2d ago First seen · 35 lines · 791 tokens per session scan A 31594ba8c7f6

Subscribe to this mod's changes

mcp-debugger AGENTS.md is an instructions file published in the GitHub repository debugmcp/mcp-debugger (159 stars, last pushed 2d ago), licensed MIT. It adds 791 tokens to every session, about $0.0040 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens