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/wilfoa/polybugger-mcp/agents-mdgit clone --depth 1 https://github.com/wilfoa/polybugger-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/wilfoa/polybugger-mcp/agents-md)<a href="https://agentmods.dev/instructions/wilfoa/polybugger-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wilfoa/polybugger-mcp/agents-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.00759 | $0.00759 |
| Opus 5 | $0.00380 | $0.00380 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
polybugger-mcp 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 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.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Debugger MCP
Project Overview
This is a Python MCP (Model Context Protocol) server that enables AI agents to debug Python code interactively. It translates MCP tool calls to DAP (Debug Adapter Protocol) messages for debugpy.
Tech Stack
- Language: Python 3.10+
- Framework: FastAPI with uvicorn, MCP SDK
- Debugger: debugpy (Python debugger)
- Testing: pytest with pytest-asyncio
- Package Manager: pip with pyproject.toml
Project Structure
src/polybugger_mcp/
api/ # FastAPI routers (sessions, breakpoints, execution, inspection, output)
adapters/ # DAP client and debugpy adapter
core/ # Session management, events, exceptions
models/ # Pydantic models (DAP, requests, responses)
persistence/ # Breakpoint storage
utils/ # Output buffer
config.py # Pydantic Settings configuration
main.py # FastAPI app entry point
mcp_server.py # MCP server with debug_* tools
tests/
unit/ # Unit tests for buffer and persistence
integration/ # API integration tests
e2e/ # End-to-end debug session tests
Running the Project
# Activate virtual environment
source .venv/bin/activate
# Start the HTTP server
python -m polybugger_mcp.main
# Start the MCP server (stdio)
python -m polybugger_mcp.mcp_server
# Run tests
pytest tests/ -v
Debugging This Project
This project includes its own debugging tools as MCP tools.
Using the Debug Tools
-
Start the MCP server - Configure your MCP client to use:
{ "mcpServers": { "python-debugger": { "command": "uvx", "args": ["polybugger-mcp"] } } } -
Use the debug_ tools* to debug Python code in this project:
debug_create_session- Create a session with project_rootdebug_set_breakpoints- Set breakpoints in source filesdebug_launch- Launch test scripts or the server itselfdebug_get_stacktrace,debug_get_variables,debug_evaluate- Inspect state
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 · 96 lines · 759 tokens per session scan A f7811bb55be6
polybugger-mcp AGENTS.md is an instructions file published in the GitHub repository wilfoa/polybugger-mcp (2 stars, last pushed 7mo ago), licensed MIT. It adds 759 tokens to every session, about $0.0038 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-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.