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/coykto/debug_mcp/claude-mdgit clone --depth 1 https://github.com/Coykto/debug_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/coykto/debug_mcp/claude-md)<a href="https://agentmods.dev/instructions/coykto/debug_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/coykto/debug_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.02820 | $0.02820 |
| Opus 5 | $0.01410 | $0.01410 |
| Sonnet 5 | $0.00564 | $0.00564 |
| Haiku 4.5 | $0.00282 | $0.00282 |
Grade C, and why
debug_mcp CLAUDE.md scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- AWS profiles (`~/.aws/credentials`) How it starts
The opening of the file, as written. The whole thing — 328 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
Debug MCP is an open-source MCP (Model Context Protocol) server for debugging distributed systems (starting with AWS: Lambda, Step Functions, ECS) directly from Claude Code or any MCP client. The project aims to eliminate context switching between console interfaces by bringing debugging capabilities into AI coding assistants.
Current Status: Direct Tool Registration - Tools are exposed directly to MCP clients (no gateway). Only tools for configured services are registered, allowing selective tool exposure based on provided credentials.
Development Commands
Environment Setup
# Install dependencies
uv sync
# Install with dev dependencies
uv sync --dev
# Run the MCP server locally
uv run debug-mcp
# Run in development mode from project root
uv run python -m debug_mcp
Testing
# Run all tests
uv run pytest
# Run tests with coverage
uv run pytest --cov=src/debug_mcp
# Run specific test file
uv run pytest tests/test_cloudwatch_logs.py
Code Quality
Pre-commit handles linting and formatting automatically. Setup:
uv sync --dev
uv run pre-commit install
Manual Testing
# Test AWS client factory in Python REPL
uv run python
>>> from debug_mcp.aws.client_factory import AWSClientFactory
>>> from debug_mcp.tools.cloudwatch_logs import CloudWatchLogsTools
>>> factory = AWSClientFactory()
>>> tools = CloudWatchLogsTools(factory)
>>> tools.describe_log_groups(prefix="/aws/lambda/")
Architecture
Project Structure
The project uses direct tool registration with conditional loading based on credentials:
src/debug_mcp/
├── server.py # Main MCP server, conditional tool registration
├── __main__.py # Entry point, CLI argument parsing
└── tools/
├── cloudwatch_logs.py # CloudWatch implementation (boto3)
├── cloudwatch_registry.py # CloudWatch tool registration
├── stepfunctions.py # Step Functions implementation (boto3)
├── stepfunctions_registry.py # Step Functions tool registration
├── langsmith.py # LangSmith implementation (SDK)
├── langsmith_registry.py # LangSmith tool registration
├── jira.py # Jira implementation (SDK)
└── jira_registry.py # Jira tool registration
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 · 328 lines · 2,820 tokens per session scan C 24def81094f5
debug_mcp CLAUDE.md is an instructions file published in the GitHub repository Coykto/debug_mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 2,820 tokens to every session, about $0.0141 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). 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.