kicad-happy is a collection of coding-agent skills and tools that inspect KiCad schematics, PCB layouts, and Gerber files for electronics design issues. It is for hardware designers who want automated reviews, simulations, datasheet checks, component sourcing, and fabrication preparation. The catalogue entries are its agent skills, rules, plugin, and instruction for integrating this workflow with coding agents.
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 aklofas/kicad-happy --skill kicadgit clone --depth 1 https://github.com/aklofas/kicad-happyWrote 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/aklofas/kicad-happy/kicad)<a href="https://agentmods.dev/skills/aklofas/kicad-happy/kicad"><img src="https://agentmods.dev/badge/skills/aklofas/kicad-happy/kicad/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/aklofas/kicad-happy/kicad"><img src="https://agentmods.dev/badge/skills/aklofas/kicad-happy/kicad.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- medium Excessive Agency · line 79 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 472 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 480 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00240 | $0.18582 |
| Opus 5 | $0.00120 | $0.09291 |
| Sonnet 5 | $0.00048 | $0.03716 |
| Haiku 4.5 | $0.00024 | $0.01858 |
Grade A, and why
kicad 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 6d 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 — 851 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KiCad Project Analysis Skill
Related Skills
| Skill | Purpose |
|---|---|
bom |
BOM extraction, enrichment, ordering, and export workflows |
digikey |
Search DigiKey for parts (prototype sourcing) |
mouser |
Search Mouser for parts (secondary prototype source) |
lcsc |
Search LCSC for parts (production sourcing, JLCPCB) |
element14 |
Search Newark/Farnell/element14 (international sourcing, reliable datasheets) |
jlcpcb |
PCB fabrication & assembly ordering |
pcbway |
Alternative PCB fabrication & assembly |
spice |
SPICE simulation verification of detected subcircuits |
emc |
EMC pre-compliance risk analysis — consumes schematic + PCB analyzer output |
Handoff guidance: Use this skill to parse schematics/PCBs and extract structured data. Hand off to bom for BOM enrichment, pricing, and ordering. Hand off to digikey/mouser/lcsc/element14 for part searches and datasheet fetching. Hand off to jlcpcb/pcbway for fabrication ordering and DFM rule validation. Always run spice for simulation verification during design reviews when any SPICE simulator is installed (check with which ngspice ltspice xyce). Always run emc for EMC pre-compliance risk analysis during design reviews when both schematic and PCB analysis are available. These are not optional — skipping them leaves value-computation errors and EMC risks undetected.
Before analysis: When the user asks to analyze or review a KiCad project, check whether a datasheets/ directory exists in the project. If not, and DigiKey API keys are available (DIGIKEY_CLIENT_ID), offer to sync datasheets first: "I can download datasheets for your components before analysis — this enables pin-level verification and decoupling validation against manufacturer specs. Want me to sync them?" If the user declines or no API keys are set, proceed without datasheets — the analysis works without them but datasheet verification findings won't be available.
What ships with it
60 files 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.
- references/config-reference.md 14 KB
- references/datasheet-verification.md 15 KB
- references/deep-review.md 7.5 KB
- references/design-intent.md 5.4 KB
- references/diff-analysis.md 14 KB
- references/file-formats.md 13 KB
- references/gerber-parsing.md 29 KB
- references/manual-gerber-parsing.md 22 KB
- references/manual-pcb-parsing.md 16 KB
- references/manual-schematic-parsing.md 13 KB
- references/net-tracing.md 11 KB
- references/oshwa-certification.md 4.5 KB
- references/output-schema.md 28 KB
- references/pcb-layout-analysis.md 26 KB
- references/pdf-schematic-extraction.md 15 KB
- references/report-generation.md 55 KB
- references/schematic-analysis.md 63 KB
- references/standards-compliance.md 33 KB
- references/supplementary-data-sources.md 12 KB
- references/what-if.md 17 KB
- review/fixtures/deep_review.example.json 1.2 KB
- review/fixtures/design_context.example.json 388 B
- review/fixtures/review_annotations.example.json 707 B
- review/prompts/design_context.md 4.9 KB
- review/README.md 4.0 KB
- review/schemas/deep_review.schema.json 3.3 KB
- review/schemas/design_context.schema.json 2.3 KB
- review/schemas/review_annotations.schema.json 1.9 KB
- review/scripts/_mini_jsonschema.py 6.6 KB runs code
- review/scripts/build_review_plan.py 1.9 KB runs code
- review/scripts/deep_review_gate.py 13 KB runs code
- review/scripts/merge_annotations.py 6.6 KB runs code
- review/scripts/run_phase4_exercise.py 12 KB runs code
- review/scripts/validate_review.py 2.2 KB runs code
- scripts/.gitignore 13 B
- scripts/analysis_cache.py 21 KB runs code
- scripts/analyze_gerbers.py 64 KB runs code
- scripts/analyze_pcb.py 293 KB runs code
- scripts/analyze_schematic.py 433 KB runs code
- scripts/analyze_thermal.py 47 KB runs code
- scripts/analyzer_envelope.py 15 KB runs code
- scripts/bus_resolver.py 12 KB runs code
- scripts/capability_mode.py 7.3 KB runs code
- scripts/check_report_sections.py 8.9 KB runs code
- scripts/cross_analysis.py 54 KB runs code
- scripts/cross_verify.py 22 KB runs code
- scripts/detection_schema.py 23 KB runs code
- scripts/detector_helpers.py 2.6 KB runs code
- scripts/diff_analysis.py 60 KB runs code
- scripts/domain_detectors.py 255 KB runs code
- scripts/envelopes/__init__.py 0 B runs code
- scripts/envelopes/cross_analysis.py 5.7 KB runs code
- scripts/envelopes/gerber.py 16 KB runs code
- scripts/envelopes/pcb.py 20 KB runs code
- scripts/envelopes/schematic.py 23 KB runs code
- scripts/envelopes/thermal.py 5.5 KB runs code
- scripts/export_issues.py 17 KB runs code
- scripts/fab_release_gate.py 23 KB runs code
- scripts/finding_schema.py 27 KB runs code
- scripts/gen_output_schema_md.py 8.6 KB runs code
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.
- 6d ago Changed 3cca142cc352
- 11d ago First seen · 851 lines · 240 tokens per session scan A e53345b79c2b
kicad is a skill published in the GitHub repository aklofas/kicad-happy (1,175 stars, last pushed 9d ago), licensed MIT. It adds 240 tokens to every session and 18,582 once invoked, about $0.0012 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
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"…
circuit-design
Use when designing an electronic circuit from requirements, choosing topology or regulator type, selecting component values, planning protection circuits, or deciding what goes on a board before schematic capture begins. Also use when the user asks "what components do I need" or "how should I power this.".
using-kicad
Use when starting any conversation involving electronics, KiCad, PCB design, schematic capture, circuit design, or EDA tasks.
schematic-plan
Use after circuit-design produces a validated BOM (specs/bom.md) to plan exact component placement coordinates and wiring before schematic capture begins. Pure planning — no file modifications.
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…