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 Avinash1286/KiCAD-MCP-Server-THEAVI --skill pcb-designgit clone --depth 1 https://github.com/Avinash1286/KiCAD-MCP-Server-THEAVIWrote 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/avinash1286/kicad-mcp-server-theavi/pcb-design)<a href="https://agentmods.dev/skills/avinash1286/kicad-mcp-server-theavi/pcb-design"><img src="https://agentmods.dev/badge/skills/avinash1286/kicad-mcp-server-theavi/pcb-design/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/avinash1286/kicad-mcp-server-theavi/pcb-design"><img src="https://agentmods.dev/badge/skills/avinash1286/kicad-mcp-server-theavi/pcb-design.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.00783 |
| Opus 5 | $0.00032 | $0.00392 |
| Sonnet 5 | $0.00013 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
pcb-design 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 10d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KiCad PCB engineering workflow
Use the KiCad MCP tools for project state and file changes. Treat the model as an engineering assistant: make assumptions explicit, verify each stage, and never describe a board as production-ready solely because ERC or DRC passes.
Start with an engineering brief
Before editing, identify the design's:
- purpose and operating environment;
- supply inputs, rails, current, and power budget;
- external interfaces, signal speeds, connectors, and pinouts;
- mechanical envelope, mounting, layer-count, and fabrication limits;
- compliance, isolation, temperature, test, cost, and sourcing constraints.
Ask only for missing information that would materially change the architecture or create a safety risk. For other gaps, choose conservative defaults and record them as assumptions.
Work through gated stages
- Inspect or create the project and summarize the current state.
- Choose a circuit architecture and explain important tradeoffs.
- Select real components from authoritative datasheets. Record manufacturer part numbers, ratings, tolerances, derating, lifecycle or sourcing concerns, and suitable footprints.
- Capture the schematic in functional blocks. Add power flags, decoupling, protection, programming or debug access, test points, labels, and connector pin descriptions.
- Run ERC. Resolve genuine errors and explain every intentional exception; do not hide problems with blanket exclusions.
- Assign and verify footprints. Check pin numbering, polarity, package dimensions, courtyard, assembly orientation, and hand-soldering or manufacturing needs.
- Define the board stack, outline, mounting, keepouts, net classes, clearances, widths, vias, differential pairs, impedance constraints, and high-voltage creepage before routing.
- Place by electrical function. Prioritize return paths, decoupling loop area, switching-current loops, crystal and analog sensitivity, thermal paths, connector mechanics, and inspectability.
- Route critical nets first, then remaining nets. Maintain continuous return paths and avoid unjustified vias or layer changes.
- Add planes, copper pours, thermal relief, stitching vias, readable silkscreen, reference designators, polarity marks, pin-one marks, test points, and revision identification.
- Run DRC and relevant design audits. Fix the design until remaining findings are explicitly justified.
- Generate and inspect the requested manufacturing package: Gerbers, drill files, BOM, position files, drawings, PDFs, STEP, and source files as applicable.
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.
- 10d ago First seen · 58 lines · 65 tokens per session scan A 93b83d74cede
pcb-design is a skill published in the GitHub repository Avinash1286/KiCAD-MCP-Server-THEAVI (0 stars, last pushed 7d ago), licensed MIT. It adds 65 tokens to every session and 783 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-31.
Other skills, from other repositories
kicad-library
Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Triggers on: "create a symbol", "make a footprint", "custom component", "register library", "find a part", "pin numbering", "new symbol", "new footprint", "add to library", "library path", "pad layout".
kicad-pcb
Workflow skill for KiCAD PCB layout and routing via MCP tools. Triggers on: "layout the board", "route traces", "PCB", "place footprints", "copper pour", "board outline", "differential pair", "board setup", "track width", "via", "zone", "design rules", "stackup", "silkscreen".
kicad-review
Design review and validation workflow for KiCAD projects via MCP tools. Triggers on: "review my design", "check for errors", "audit", "DRC", "ERC", "find problems", "design review", "is this ready", "validate", "check my schematic", "check my PCB", "what's wrong", "run checks", "pre-fab review".
kicad-schematic
Workflow skill for KiCAD schematic design via MCP tools. Triggers on: "design a circuit", "add a component", "wire up", "connect pins", "build schematic", "place resistor", "place cap", "place IC", "schematic", "add symbol", "net label", "power rail".
kicad-manufacture
Manufacturing and fabrication workflow for KiCAD projects via MCP tools. Triggers on: "send to fab", "order boards", "gerbers", "JLCPCB", "manufacturing", "export for production", "pick and place", "assembly files", "generate fabrication outputs", "BOM for fab", "production files", "fab house".
konnect
Mandatory operating rules for ANY task involving KiCAD projects. Loaded when the user mentions KiCAD, schematics, PCBs, or any .kicad file. Prevents file corruption by routing all changes through Konnect MCP tools.