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 lcscgit 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/lcsc)<a href="https://agentmods.dev/skills/aklofas/kicad-happy/lcsc"><img src="https://agentmods.dev/badge/skills/aklofas/kicad-happy/lcsc/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/lcsc"><img src="https://agentmods.dev/badge/skills/aklofas/kicad-happy/lcsc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00174 | $0.02672 |
| Opus 5 | $0.00087 | $0.01336 |
| Sonnet 5 | $0.00035 | $0.00534 |
| Haiku 4.5 | $0.00017 | $0.00267 |
Grade A, and why
lcsc scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **OS-agnostic** — uses `requests` → `urllib` → `playwright` fallback chain (no wget/curl) How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LCSC Electronics — Component Search, Datasheets & Ordering
Related Skills
| Skill | Purpose |
|---|---|
kicad |
Schematic analysis — extracts MPNs for part lookup |
bom |
BOM management — orchestrates sourcing across distributors |
jlcpcb |
PCB assembly — shares the same parts library |
spice |
Uses LCSC parametric data for behavioral SPICE models (no auth needed) |
LCSC is JLCPCB's sister company — they share the same parts library and Cxxxxx part numbers. Use LCSC for production sourcing (assembled boards from JLCPCB/PCBWay). DigiKey/Mouser are for prototyping. For BOM management and export workflows, see bom.
Key Differences from DigiKey/Mouser
- No API key needed — jlcsearch community API is free and open
- Lower prices — especially for passives and Chinese-manufactured ICs
- JLCPCB integration — same LCSC part numbers used in JLCPCB assembly BOMs
- Direct PDF downloads — LCSC's CDN (wmsc.lcsc.com) serves datasheets without bot protection
- Low MOQ — many parts available in quantities as low as 1
- Warehouses — Shenzhen (JS), Zhuhai (ZH), Hong Kong (HK)
- Website:
https://www.lcsc.com
LCSC Part Numbers
Format: Cxxxxx (e.g., C14663). This is the universal identifier across both LCSC and JLCPCB. Use it for:
- Direct ordering on LCSC
- BOM matching in JLCPCB assembly (see
jlcpcbskill) - Cross-referencing between platforms
jlcsearch API Reference
The jlcsearch community API is the recommended way to search LCSC. No authentication required.
Base URL: https://jlcsearch.tscircuit.com
General Search
GET /api/search?q=<query>&limit=20&full=true
Parameters:
q— search query (matches MPN, LCSC code, or description keywords)package— optional footprint filter (e.g.,0402)limit— max results (default 100)full— set totrueto include all fields (datasheet URL, specs, stock per warehouse)
Category-Specific Search
GET /resistors/list.json?search=10k+0402
GET /capacitors/list.json?search=100nF+0402
GET /microcontrollers/list.json?search=STM32
GET /voltage_regulators/list.json?search=3.3V
What ships with it
2 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.
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.
- 11d ago First seen · 224 lines · 174 tokens per session scan A 1d295aa3f4e1
lcsc is a skill published in the GitHub repository aklofas/kicad-happy (1,166 stars, last pushed 9d ago), licensed MIT. It adds 174 tokens to every session and 2,672 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…