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 agents/oaslananka/kicad-mcp-pro/claude-codegit clone --depth 1 https://github.com/oaslananka/kicad-mcp-proWrote 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/agents/oaslananka/kicad-mcp-pro/claude-code)<a href="https://agentmods.dev/agents/oaslananka/kicad-mcp-pro/claude-code"><img src="https://agentmods.dev/badge/agents/oaslananka/kicad-mcp-pro/claude-code.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.1 | $0.00000 | $0.00408 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
claude-code 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 6d 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.
What it actually says
Claude Code Integration
Quick Start
claude mcp add --transport stdio --scope project kicad -- uvx kicad-mcp-pro
Or with project scope .mcp.json:
{
"mcpServers": {
"kicad": {
"type": "stdio",
"command": "uvx",
"args": ["kicad-mcp-pro"],
"env": {
"KICAD_MCP_PROJECT_DIR": "${CLAUDE_PROJECT_DIR:-.}",
"KICAD_MCP_PROFILE": "default",
"KICAD_MCP_OPERATING_MODE": "readonly"
}
}
}
}
Skill Installation
cp -r integrations/claude-code/kicad-pcb-review-skill ~/.claude/skills/
The skill auto-loads for KiCad PCB review tasks.
Verification
/mcp → list connected servers
Example Prompts
Read-only inspection
Use the kicad MCP server. Inspect this KiCad project, identify the board, schematic, KiCad version, run the available quality gates, and summarize whether the project is ready for PCB review. Do not modify files.
ERC/DRC
Use kicad MCP read-only tools to run ERC and DRC. Group issues by severity, explain likely causes, and propose a safe fix plan. Do not edit until I approve.
Manufacturing
Use kicad MCP to check whether this board is manufacturing-ready for JLCPCB/PCBWay. Run quality gates, inspect BOM/POS/export readiness, and produce a release checklist. Do not generate files yet.
Write (guarded)
Use kicad MCP to fix the approved issue only. Before any write operation, show the exact tool and intended change. After editing, run ERC/DRC and summarize changed files.
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.
- 6d ago First seen · 55 lines · 0 tokens per session scan A 075ce725183e
claude-code is an agent published in the GitHub repository oaslananka/kicad-mcp-pro (64 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 408 tokens. 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 agents, from other repositories
index
This section centralizes the instructions and client configuration surfaces used by coding agents and MCP-capable clients that work with KiCad Studio Kit.
client-configs
KiCad MCP Pro supports local stdio and Streamable HTTP MCP transports. The canonical copyable examples live under examples/mcp-clients/.
codex-support
KiCad Studio Kit supports Codex through the external MCP client path.
bom-reviewer
You are a reviewer subagent. Your job is to independently verify a BOM artifact produced by the circuit-design skill. You have access to all KiCad MCP tools.
schematic-plan-reviewer
You are a reviewer subagent. Your job is to independently verify a schematic placement and wiring plan artifact. You have access to all KiCad MCP tools.
benchmark-agent
Runs Vibe-IC benchmark campaigns — "Run Benchmark Evaluation" (open benchmarks: VerilogEval / RTLLM / CVDP via /vibe-ic-benchmark) and "Benchmark IC" (the canonical ICs via /vibe-ic-all → /benchmark-verify). Commits + pushes results under benchmark-data/. When it finds a chip-AGNOSTIC plugin/MCP gap it AUTHORS the fix…