Borrowing it
Nothing to install: this file belongs to drandyhaas/KiCadRoutingTools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/drandyhaas/KiCadRoutingTools/main/.claude/skills/review-routed-board/SKILL.mdgit 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/review-routed-board)<a href="https://agentmods.dev/skills/drandyhaas/kicadroutingtools/review-routed-board"><img src="https://agentmods.dev/badge/skills/drandyhaas/kicadroutingtools/review-routed-board/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/drandyhaas/kicadroutingtools/review-routed-board"><img src="https://agentmods.dev/badge/skills/drandyhaas/kicadroutingtools/review-routed-board.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.00083 | $0.03497 |
| Opus 5 | $0.00042 | $0.01749 |
| Sonnet 5 | $0.00017 | $0.00699 |
| Haiku 4.5 | $0.00008 | $0.00350 |
Grade A, and why
review-routed-board 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 3d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Routed Board
When this skill is invoked with a board file, run a full post-route review and present a sign-off report.
Step 1: Mechanical Checks
Run all four checkers, capturing output:
python3 -X utf8 py_router/check_drc.py board.kicad_pcb 2>&1 | tee /tmp/review_drc.txt
python3 -X utf8 py_router/check_connected.py board.kicad_pcb 2>&1 | tee /tmp/review_connectivity.txt
python3 -X utf8 py_tools/check_orphan_stubs.py board.kicad_pcb 2>&1 | tee /tmp/review_orphans.txt
python3 -X utf8 py_router/check_weird.py board.kicad_pcb 2>&1 | tee /tmp/review_weird.txt
check_weird.py is here because the other three cannot see its classes.
check_orphan_stubs iterates SEGMENT endpoints and treats a via as an anchor,
so it structurally cannot report a bad via; check_weird owns dangling-via
(same-net copper on only one of the layers the barrel spans -- KiCad's
via_dangling), unsupported-via, stacked-copper and orphan-island.
Measured on run 11's final board: check_orphan_stubs none, check_weird
3 dangling vias, each independently confirmed.
check_drc.py auto-grades at the clearance the routing steps wrote into the sibling
.kicad_pro (the smallest clearance any step actually used, including auto-stepped
fine-pitch taps), so the bare invocation above already grades at the true routed
floor. Pass --clearance <value> only to override (e.g. to grade a hand-routed
board with no routed-floor .kicad_pro).
Important caveat to include in the report: check_drc.py does not check zone copper, minimum trace width, or netclass compliance. If the board has copper zones/planes, recommend the zone-aware check:
kicad-cli pcb drc board.kicad_pcb --refill-zones --format json -o /tmp/drc.json
Ignore silk and dangling violations when reading that report — they are not
routing/connectivity defects and are excluded by the harness graders
(kicad_drc_compare.py, kicad_oracle.py) for exactly this reason. Filter them
out before counting:
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.
- 3d ago Changed 57c6ab746616
- 13d ago First seen · 263 lines · 83 tokens per session scan A 7482bb184d9c
review-routed-board is a skill published in the GitHub repository drandyhaas/KiCadRoutingTools (407 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 3,497 once invoked, about $0.0004 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
boardrepo
Read and review real PCB projects on BoardRepo. Search published hardware designs, open a board's schematic connectivity, bill of materials and files, run KiCad's DRC and ERC, and check a design against a fabrication house's limits. Use whenever the user names a BoardRepo board or URL, asks to find a published board…
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
code-plan
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
ros2-robotics
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…