Borrowing it
Nothing to install: this file belongs to Kaina3/Debug-MCP. 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/Kaina3/Debug-MCP/master/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Kaina3/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/kaina3/debug-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/kaina3/debug-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kaina3/debug-mcp/copilot-instructions/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/kaina3/debug-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kaina3/debug-mcp/copilot-instructions.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.00609 | $0.00609 |
| Opus 5.5 | $0.00244 | $0.00244 |
| Sonnet 5.5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Debug-MCP copilot-instructions.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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug-MCP Development Guidelines
Auto-generated from all feature plans. Last updated: 2025-10-23
Active Technologies
- Python 3.11 (tool + debug runner) + Standard library (bdb/pdb, subprocess, multiprocessing), typer/click for local CLI (optional), pydantic for schemas, pytest for tests (001-python-debug-tool)
Project Structure
src/
tests/
Commands
cd src [ONLY COMMANDS FOR ACTIVE TECHNOLOGIES][ONLY COMMANDS FOR ACTIVE TECHNOLOGIES] pytest [ONLY COMMANDS FOR ACTIVE TECHNOLOGIES][ONLY COMMANDS FOR ACTIVE TECHNOLOGIES] ruff check .
Code Style
Python 3.11 (tool + debug runner): Follow standard conventions
Recent Changes
- 001-python-debug-tool: Added Python 3.11 (tool + debug runner) + Standard library (bdb/pdb, subprocess, multiprocessing), typer/click for local CLI (optional), pydantic for schemas, pytest for tests
Python Execution Instructions
Using uv (Recommended)
Run Python files directly:
# Run a Python script
uv run python my_script.py
# Run a module
uv run python -m my_module
# Run tests
uv run pytest
# Run the MCP server
uv run mcp-debug --workspace .
# Run with coverage
uv run pytest --cov=src/mcp_debug_tool --cov-report=html
Using venv (Traditional)
Activate environment first:
# macOS/Linux
source .venv/bin/activate
# Windows
.venv\Scripts\activate
Then run normally:
python my_script.py
python -m my_module
pytest
mcp-debug --workspace .
Why uv run is better
- No activation needed: Works immediately without sourcing scripts
- Consistent environment: Always uses the correct Python and dependencies
- Cross-shell compatibility: Works the same in bash, zsh, fish, PowerShell
- Faster startup: No shell initialization overhead
- Reliable: Prevents "wrong Python" errors
Quick Reference
# Environment setup
uv venv # Create virtual environment
uv pip install -e ".[dev]" # Install project with dev deps
# Common commands
uv run pytest # Run all tests
uv run pytest tests/unit/ -v # Run unit tests verbose
uv run ruff check . # Lint code
uv run ruff check --fix . # Auto-fix lint issues
uv run ruff format . # Format code
uv run python -m mcp_debug_tool.server # Run MCP server
uv run mcp-debug --workspace . # Run MCP server (CLI)
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 · 95 lines · 609 tokens per session scan A 8ee610c3d2e4
Debug-MCP copilot-instructions.md is an instructions file published in the GitHub repository Kaina3/Debug-MCP (1 stars, last pushed 11mo ago), licensed MIT. It adds 609 tokens to every session, about $0.0024 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.