Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/drandyhaas/kicadroutingtools/plan-pcb-routing)<a href="https://agentmods.dev/skills/drandyhaas/kicadroutingtools/plan-pcb-routing"><img src="https://agentmods.dev/badge/skills/drandyhaas/kicadroutingtools/plan-pcb-routing.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.00058 | $0.42295 |
| Opus 5 | $0.00029 | $0.21147 |
| Sonnet 5 | $0.00012 | $0.08459 |
| Haiku 4.5 | $0.00006 | $0.04229 |
Grade A, and why
plan-pcb-routing 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 yesterday.
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 — 2,606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan PCB Routing
When this skill is invoked with a KiCad PCB file, perform a comprehensive analysis and present a routing plan to the user.
Step 1: Load and Analyze PCB Structure
from kicad_parser import parse_kicad_pcb
pcb = parse_kicad_pcb('path/to/file.kicad_pcb')
# Basic stats
print(f'Total nets: {len(pcb.nets)}')
print(f'Total footprints: {len(pcb.footprints)}')
print(f'Existing segments: {len(pcb.segments)}')
print(f'Existing vias: {len(pcb.vias)}')
Report to user:
- Number of nets, components, existing routing
- Whether this is a fresh board or partially routed
Step 2: Identify Copper Layers
Check the KiCad file directly for layer definitions:
grep -E "^\s+\([0-9]+ \".*\.Cu\"" path/to/file.kicad_pcb
Report to user:
- Available copper layers (F.Cu, B.Cu, In1.Cu, In2.Cu, etc.)
- Whether it's a 2-layer, 4-layer, or multi-layer board
Stackup Check (always run this early)
Inspect the stackup now, before planning, and report the verdict at the top of the plan report so problems surface before any routing work:
from kicad_parser import parse_kicad_pcb
pcb = parse_kicad_pcb('path/to/file.kicad_pcb')
for layer in pcb.board_info.stackup: # List[StackupLayer], ordered top to bottom
print(layer.name, layer.layer_type, layer.thickness, layer.epsilon_r)
- No stackup section, or all dielectrics with identical thickness and ε_r ≈ 4.5, means
KiCad's untouched default. If the board also has impedance-relevant signals (see the
speed detection in Step 4), lead the report with a clear warning: impedance and
time-matching calculations will not match the user's fab, and
/recommend-stackupshould be run before impedance-controlled routing. Take plane-layer assignments from its output when available. - A 2-layer board with multiple differential pairs or planes-worth of power nets is itself worth flagging (no inner layers for reference planes).
- If the stackup looks deliberate, say so in one line and move on.
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.
- yesterday Changed · +3 lines df2a5cd9cc77
- 2d ago Changed · +8 lines 89ebd01b2192
- 6d ago First seen · 2,595 lines · 58 tokens per session scan A 878fe8db8ef0
plan-pcb-routing is a skill published in the GitHub repository drandyhaas/KiCadRoutingTools (382 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 42,295 once invoked, about $0.0003 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
tao-train-visual-changenet
Visual ChangeNet for binary image classification and segmentation in AOI defect detection. Use when training, evaluating, exporting, or running inference for PCB defect detection or visual inspection, comparing image pairs for PASS/NOPASS classification, or producing change-segmentation masks. Trigger phrases include…
altium-library
Create and verify Altium schematic symbols (.SchLib) and PCB footprints (.PcbLib) from datasheets and 2D drawings, as code. Use whenever a part library must be made, fixed, measured from a drawing, or checked. Triggers: "make a footprint", "create a symbol", "add this part to the library", "SchLib", "PcbLib"…
altium-pcb-placement
Altium PCB component placement — derive board size, decide rotation for main ICs and connectors, split zones, generate a 1:1 placement plan drawing, then inject real coordinates after approval, and check overlaps. Triggers: "PCB placement", "place the components", "how big should the board be", "board outline", "start…
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…
kicad-copilot-mcp
Use when KiCad Copilot MCP tools are available. Entry point for KiCad schematic and PCB workflows.
kicad-schematic-design
Create, edit, inspect, and validate KiCad schematics for digital, analog, power, interface, and mixed-signal circuits. Use for requests to open KiCad, create or draw schematics, place library symbols, assign footprints, define external interfaces, wire nets, review screenshots, or diagnose ERC and netlist issues.