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 skills add oaslananka/kicad-mcp-pro --skill kicad-pcb-review-skillgit 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/skills/oaslananka/kicad-mcp-pro/kicad-pcb-review-skill)<a href="https://agentmods.dev/skills/oaslananka/kicad-mcp-pro/kicad-pcb-review-skill"><img src="https://agentmods.dev/badge/skills/oaslananka/kicad-mcp-pro/kicad-pcb-review-skill/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/skills/oaslananka/kicad-mcp-pro/kicad-pcb-review-skill"><img src="https://agentmods.dev/badge/skills/oaslananka/kicad-mcp-pro/kicad-pcb-review-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00588 |
| Opus 5 | $0.00015 | $0.00294 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
kicad-pcb-review 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 13d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KiCad PCB Review Skill
Use this skill for KiCad projects, schematic review, PCB layout review, DRC/ERC, DFM, manufacturing exports, BOM, pick-and-place, stackup, SI/PI/EMC checks, and release package preparation.
Required Behavior
-
First verify the MCP server:
- Call
kicad_get_project_info - Call
project_quality_gate - Inspect KiCad version and project paths
- Call
-
Never edit before reading the current schematic and PCB state.
-
For design changes:
- Explain proposed change
- Use
kicad_set_projectto select the KiCad project instead of shellcdwhen possible - Use dry-run if available
- Ask for confirmation before destructive/write tools
- Prefer dedicated MCP operations over Bash/Python file rewriting; use
pcb_delete_items/pcb_delete_objectfor PCB object removal andrun_drcfor DRC verification - If the required MCP operation is not visible in the active profile/mode, stop and state which supported profile/mode is required. Do not silently fall back to
sed, regex-based Python, or direct.kicad_pcb/.kicad_schmutation
-
After any edit:
- Run ERC
- Run DRC
- Run relevant DFM checks
- Summarize files changed
-
For manufacturing release:
- Run full validation loop
- Export Gerber/drill/BOM/POS/STEP/PDF
- Generate manifest
- List warnings and waiver status
Tool Preference
Read-only first:
kicad_get_project_infosch_get_symbolssch_get_net_namespcb_get_board_summarypcb_get_netsrun_ercrun_drcvalidate_designproject_quality_gate
Write only when requested:
- Schematic add/edit tools
- PCB add/edit tools, including
pcb_delete_itemsandpcb_delete_objectfor removal - Route tools
- Export/release tools
Refusal Policy
Do not claim a board is manufacturing-ready unless ERC, DRC, DFM, BOM, POS and export checks have passed or every issue is explicitly documented.
References
See references/kicad-mcp-tool-map.md for a complete tool listing.
See references/pcb-review-checklist.md for the PCB review process.
See references/manufacturing-release-checklist.md for release preparation.
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.
- 13d ago First seen · 67 lines · 31 tokens per session scan A 8dbbaa67587b
kicad-pcb-review is a skill published in the GitHub repository oaslananka/kicad-mcp-pro (86 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 588 once invoked, about $0.0002 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
jlcpcb-headstage-pcb
A project-specific guide for reviewing and improving printed-circuit-board designs made for JLCPCB's electronics-manufacturing service. It also covers manufacturing files such as Gerbers and drill files.
rtl-review
Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.
circuit-design
Use when designing an electronic circuit from requirements, choosing topology or regulator type, selecting component values, planning protection circuits, or deciding what goes on a board before schematic capture begins. Also use when the user asks "what components do I need" or "how should I power this.".
schematic-plan
Use after circuit-design produces a validated BOM (specs/bom.md) to plan exact component placement coordinates and wiring before schematic capture begins. Pure planning — no file modifications.
using-kicad
Use when starting any conversation involving electronics, KiCad, PCB design, schematic capture, circuit design, or EDA tasks.
altium-schematic-review
Review an Altium schematic (.SchDoc) — find unconnected pins, missing footprint links and net errors, then judge each candidate against the datasheet before calling it a defect. Triggers: "review this schematic", "check my circuit", "ERC", "floating pins", "unconnected", "any missing footprints", "does this schematic…