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.
Borrowing it
Nothing to install: this file belongs to aklofas/kicad-happy. 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/aklofas/kicad-happy/main/GEMINI.mdgit 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/instructions/aklofas/kicad-happy/gemini-md)<a href="https://agentmods.dev/instructions/aklofas/kicad-happy/gemini-md"><img src="https://agentmods.dev/badge/instructions/aklofas/kicad-happy/gemini-md/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/instructions/aklofas/kicad-happy/gemini-md"><img src="https://agentmods.dev/badge/instructions/aklofas/kicad-happy/gemini-md.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.01207 | $0.01207 |
| Opus 5 | $0.00603 | $0.00603 |
| Sonnet 5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
kicad-happy GEMINI.md 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kicad-happy
AI-powered electronics design review skills for KiCad 5-10. This document is auto-loaded into the Gemini CLI context and carries project-specific guidance for agents working in this repo.
Agent guidelines
- Skill activation: invoke
activate_skillbefore running the Python scripts in this repo. Each skill'sSKILL.mdcarries procedural guidance, triggers, and constraints that aren't in the main system prompt. - Context efficiency:
- Search first: use
grep_searchto find points of interest in.kicad_schand.kicad_pcbfiles — they routinely exceed 10,000 lines. - Targeted reads: avoid reading whole schematic/PCB files. Use line numbers from
grep_searchfor surgicalread_filecalls. - Trust analyzer output: the Python analysis scripts are the source of truth for design data. Don't guess circuit behavior from raw S-expressions when a detector already covers it.
- Search first: use
- Validation: a change isn't done until the relevant
analyze_*.pyscript has been re-run and produces no new warnings or regressions.
Skills
| Skill | Purpose |
|---|---|
| kicad | Core analysis — schematic parsing, PCB layout review, Gerber verification, thermal, diff, what-if |
| datasheets | Structured datasheet extraction — per-MPN cache, quality scoring, consumer API for other skills |
| emc | EMC pre-compliance — 44 rules across 18 categories |
| spice | SPICE simulation — auto-generated testbenches, Monte Carlo tolerance |
| bom | BOM management — multi-supplier pricing, order file export |
| digikey | DigiKey API — component search, datasheet download, --mpn-list batch mode |
| mouser | Mouser API — component search, --mpn-list batch mode |
| lcsc | LCSC/JLCPCB parts — community API, no auth required, --mpn-list batch mode |
| element14 | element14/Newark/Farnell API — --mpn-list batch mode |
| jlcpcb | JLCPCB fab rules, BOM/CPL format |
| pcbway | PCBWay fab rules, turnkey assembly |
Running analysis
# Schematic analysis
python3 skills/kicad/scripts/analyze_schematic.py <file>.kicad_sch
python3 skills/kicad/scripts/analyze_schematic.py <file>.kicad_sch --output analysis.json
# PCB layout analysis
python3 skills/kicad/scripts/analyze_pcb.py <file>.kicad_pcb
python3 skills/kicad/scripts/analyze_pcb.py <file>.kicad_pcb --full --output pcb.json
# EMC pre-compliance (requires schematic + PCB JSON)
python3 skills/emc/scripts/analyze_emc.py --schematic sch.json --pcb pcb.json
# Gerber verification
python3 skills/kicad/scripts/analyze_gerbers.py <gerber_dir>/
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 · 73 lines · 1,207 tokens per session scan A 7069ad82ad8d
kicad-happy GEMINI.md is an instructions file published in the GitHub repository aklofas/kicad-happy (1,166 stars, last pushed 8d ago), licensed MIT. It adds 1,207 tokens to every session, about $0.0060 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.