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 skills/ai-debugger-inc/aidb/mcp-tools-developmentnpx skills add ai-debugger-inc/aidb --skill mcp-tools-developmentgit clone --depth 1 https://github.com/ai-debugger-inc/aidbWrote 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/skills/ai-debugger-inc/aidb/mcp-tools-development)<a href="https://agentmods.dev/skills/ai-debugger-inc/aidb/mcp-tools-development"><img src="https://agentmods.dev/badge/skills/ai-debugger-inc/aidb/mcp-tools-development.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.00015 | $0.02871 |
| Opus 5 | $0.00008 | $0.01435 |
| Sonnet 5 | $0.00003 | $0.00574 |
| Haiku 4.5 | $0.00002 | $0.00287 |
Grade A, and why
mcp-tools-development 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 5d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tools Development Skill
This skill guides you through creating and modifying MCP tools for the AI Debugger (AIDB). MCP tools are the primary interface between AI agents and the debugging system - they must be fast, accurate, and clear.
Core Philosophy: Agent Optimization
MCP tools are user-facing products. Every response is read by an AI agent with limited context. Your goal:
- Accuracy: Responses must contain correct information (line numbers, values, state)
- Clarity: Summaries must be clear and actionable, not verbose
- Speed: Operations must be fast (agents iterate rapidly)
- No Junk: No unnecessary fields, no bloated payloads, no redundant data
Context windows are sacred - every token matters.
Quick Start
When to Use This Skill
Invoke this skill when:
- Creating a new MCP tool (e.g.,
aidb.watchfor watchpoints) - Modifying existing tool behavior
- Fixing MCP response issues
- Optimizing tool performance
- Debugging tool handler errors
Related Skills
When developing MCP tools, you may also need:
- dap-protocol-guide - MCP tools use DAP types for all debugging operations
- testing-strategy - MCP tools tested with DebugInterface for content accuracy
- code-reuse-enforcement - Must use existing constants/enums from core package
MCP Architecture Overview
For complete MCP server architecture, see:
docs/developer-guide/overview.md- System architecture showing MCP layer integrationsrc/aidb_mcp/- MCP server implementation
User Request
↓
MCP Server (src/aidb_mcp/server/)
↓
Handler Registry (src/aidb_mcp/handlers/registry.py)
↓
Tool Handler (src/aidb_mcp/handlers/{category}/)
↓
DebugService (src/aidb/service/)
↓
Response Builder (src/aidb_mcp/responses/)
↓
MCP Response
Key Components:
- Tool Definitions (
src/aidb_mcp/tools/definitions.py): Tool schemas and metadata - Handler Registry (
src/aidb_mcp/handlers/registry.py): Dispatcher to handlers - Tool Handlers (
src/aidb_mcp/handlers/{category}/): Business logic - Response Builders (
src/aidb_mcp/responses/): Standardized response construction - Decorators (
src/aidb_mcp/core/decorators.py): Common handler functionality
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 355 lines · 15 tokens per session scan A 129c93cdf18f
mcp-tools-development is a skill published in the GitHub repository ai-debugger-inc/aidb (21 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 2,871 once invoked, about $0.0001 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.
Other skills, from other repositories
release-notes
Draft concise release notes.
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
neuron-test-engineer
Write tests for Neuron AI agents, RAG systems, workflows, and tools using the built-in testing utilities. Use this skill when the user mentions testing agents, writing unit tests, mocking AI providers, testing tool execution, verifying RAG retrieval, testing workflow behavior, or creating test cases for Neuron AI…
neuron-tool-creator
Create custom tools, toolkits, and MCP integrations for Neuron AI agents. Use this skill when the user mentions creating tools, building toolkits, extending Tool class, defining tool properties, implementing tool execution, MCP server integration, Model Context Protocol, connecting external tools, or tool guidelines.…
neuron-workflow-architect
Build custom Neuron AI workflows with nodes, events, middleware, and human-in-the-loop patterns. Use this skill whenever the user mentions workflows, orchestration, event-driven systems, custom agents, complex multi-step processes, human-in-the-loop patterns, or wants to build a custom agentic system from scratch.…