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/drandyhaas/kicadroutingtools/plan-pcb-placementnpx skills add drandyhaas/KiCadRoutingTools --skill plan-pcb-placementgit clone --depth 1 https://github.com/drandyhaas/KiCadRoutingToolsWrote 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-placement)<a href="https://agentmods.dev/skills/drandyhaas/kicadroutingtools/plan-pcb-placement"><img src="https://agentmods.dev/badge/skills/drandyhaas/kicadroutingtools/plan-pcb-placement.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.00115 | $0.21738 |
| Opus 5 | $0.00057 | $0.10869 |
| Sonnet 5 | $0.00023 | $0.04348 |
| Haiku 4.5 | $0.00012 | $0.02174 |
Grade A, and why
plan-pcb-placement 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 today.
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 — 1,426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan PCB Placement
Placement decides what routing can achieve, and a wrong placement cannot be rescued by any router. This skill owns that half: deciding whether to touch the placement at all, fixing it when it is wrong, and proving the fix.
It never routes. When the board is placed and you want copper, use
/plan-pcb-routing. When one run must do both, use
/plan-pcb-placement-and-routing, which sequences the two and owns the rules
that only exist when they meet.
What you are optimising FOR
A board that ROUTES: parts arranged so they work together, ending at zero
unrouted and zero broken. Not parts returned to the poses they used to
have. On a repair or reconstruction job this distinction decides which result
you call a success.
- Lead with the routed outcome.
board_score'sblocking—unrouted + brokenfirst — thenqualityas the tie-break once it is 0. - On the perturbed corpus,
recoveryandhome /Nare DIAGNOSTICS, not the score. They measure distance to the original pose. Measured (run 10):recovery−0.0014,home0/30, on a run that took copper-free DRC 9 → 0, assembly blocking 4 → 0, and the board from NOT BUILDABLE to buildable. The one recovery figure that IS a defect signal iscollateral_pad_rmsrising — that means parts nothing had damaged were moved. - A human original is a benchmark to approach (its vias / copper / segment counts), not a pose to match.
The top-priority defect: pad copper off the outline
Ahead of every clearance graze. Those nets cannot be routed at all, so the
defect converts one-for-one into unrouted and broken. Measured, run 10: 11
such parts caused ALL 13 unrouted nets and most of 37 broken ones.
Read it from render_placement --json-out's
checklist.a_off_outline.pad_copper. A whole-board pass/fail verdict is the
wrong channel to learn it from — check the per-part list.
Scope the search to the refs the gate names
When a gate names specific parts, free exactly those and lock everything else. A whole-board sweep orders its violators by its own priority — usually worst-off-board first — and may never reach the ones blocking you. Measured: 2 parts freed and 105 locked cleared both blocking pairs in 63 seconds, where whole-board sweeps ran 10+ minutes without touching them.
What ships with it
1 file 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.
- today Changed 2a8d4b9c1502
- yesterday Changed · +119 lines 63dcab2c6513
- 6d ago First seen · 1,307 lines · 115 tokens per session scan A 7c501bb5fa29
plan-pcb-placement is a skill published in the GitHub repository drandyhaas/KiCadRoutingTools (382 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 21,738 once invoked, about $0.0006 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…
cad-skills
Use when doing parametric 3D modeling, 2D drafting, geometric kernel development, BIM/IFC processing, PCB design, or AutoCAD .NET development. Index of 20 skills: FreeCAD, OpenSCAD, OCCT, CadQuery, KiCad, SolveSpace, QCAD, xBIM, Clipper2, TongWen and more.
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.