plan-pcb-routing

plan-pcb-routing is a skill for Claude Code from drandyhaas/KiCadRoutingTools. It costs 58 tokens per session (42,295 once invoked), scanned A, original, MIT.

A workflow for examining a KiCad PCB design and planning how its copper connections should be routed. KiCad is software for designing printed circuit boards, and routing means drawing the copper paths that connect components.

In plain words
What is it for?
Use it to inspect a `.kicad_pcb` file, report its nets, components, existing routes, and copper layers, identify routing priorities, and produce a step-by-step plan for completing the board.
Why use it?
It identifies connections that need special treatment, such as high-speed differential pairs, power and ground nets, and dense chip fanouts, before routing begins. It also checks the board's copper-layer setup for problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is python3 py_router/list_nets.py path/to/file.kicad_pcb --diff-pairs --power.

Install

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.

Made for: Claude Code.

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.

agentmods badge for plan-pcb-routing

README.md
[![agentmods](https://agentmods.dev/badge/skills/drandyhaas/kicadroutingtools/plan-pcb-routing.svg)](https://agentmods.dev/skills/drandyhaas/kicadroutingtools/plan-pcb-routing)
Your own site
<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>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 42,295 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash df2a5cd9cc77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.claude/skills/plan-pcb-routing/SKILL.md · 2,606 lines

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-stackup should 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.

Read the full file on GitHub · 2,606 lines

Changes

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.

  1. yesterday Changed · +3 lines df2a5cd9cc77
  2. 2d ago Changed · +8 lines 89ebd01b2192
  3. 6d ago First seen · 2,595 lines · 58 tokens per session scan A 878fe8db8ef0

Subscribe to this mod's changes

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.

Related

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…

NVIDIA-TAO/tao-skill-bank · 92 tokens

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"…

ScottJeong/altium-claude-skills · 256 tokens

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…

ScottJeong/altium-claude-skills · 250 tokens

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…

ScottJeong/altium-claude-skills · 251 tokens

kicad-copilot-mcp

Use when KiCad Copilot MCP tools are available. Entry point for KiCad schematic and PCB workflows.

biosshot/kicad-copilot · 30 tokens

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.

Seahan1/kicad-agent · 73 tokens