A beginner-focused workflow for designing small printed circuit boards, or PCBs, from a written specification into KiCad files ready for review and fabrication. KiCad is software for drawing electronic schematics and board layouts; ERC and DRC are checks for electrical and physical design errors.

Use it to create or modify small development boards, module carriers, audio boards, and sensor boards. It covers requirements, pin and part mapping, scripted schematic and layout generation, ERC/DRC checks, 3D review, and fab-order files.

It replaces manual layout work with repeatable scripts and shared source files, reducing the risk that the schematic, board, enclosure, and firmware disagree. It also includes checks and fabrication-package preparation.

vibe-pcb — Skill for Claude Code and Codex by luckiday

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/luckiday/vibe-hardware

agentmods

npx agentmods add skills/luckiday/vibe-hardware/vibe-pcb

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/luckiday/vibe-hardware/vibe-pcb.svg)](https://agentmods.dev/skills/luckiday/vibe-hardware/vibe-pcb)

Your own site

<a href="https://agentmods.dev/skills/luckiday/vibe-hardware/vibe-pcb"><img src="https://agentmods.dev/badge/skills/luckiday/vibe-hardware/vibe-pcb.svg" alt="Measured on agentmods" height="20"></a>

Per session 353 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,605 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00353	$0.03605
Opus 5	$0.00177	$0.01802
Sonnet 5	$0.00071	$0.00721
Haiku 4.5	$0.00035	$0.00361

Measured 7d ago against content hash 5d82c457aa55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

vibe-pcb 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 7d ago.

The scan reads SKILL.md. This mod also ships 18 executable files (scripts/_kicad_env.sh, scripts/autoroute.sh, scripts/belly_check.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/vibe-pcb/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Text → PCB (beginner + Claude Code → fab order)

A reproducible pipeline for small boards (module-carriers, audio boards, sensor tiles). You write the intent in prose; Claude Code emits KiCad by script, drives ERC/DRC to clean, reviews it, fits it in 3D, and packages the fab order. You never hand-place a track in a GUI.

Proven on a 70×70 mm ESP32-S3 + dual-codec speaker board, generated end to end with the method below (contracts → relations → gates → scripted route → DRC 0/0). The war stories throughout are from that build.

Why "by script", not the KiCad GUI

The .kicad_sch / .kicad_pcb are outputs (gitignored, regenerated). The sources of truth are data files + two small generators:

Source	Owns	Consumed by
`../cad/constraints.yaml`	outline, mount holes, port/window positions, keepouts	`pcblib.Board` draws them; the enclosure model reads the same file
`pinmap.yaml`	signal ↔ GPIO (the pcb→firmware contract)	firmware header; `plm_check.py` cross-checks
`parts.yaml`	ref → footprint/value/pad→net map/cluster/DNP/LCSC	both generators — sch and pcb cannot drift
`gen_sch.py`	symbol grid + labels (via `pcblib.sch`)	`.kicad_sch`
`gen_pcb.py`	placement relations + routing (via `pcblib`)	`.kicad_pcb`, `placement.json`, `board.step`

The representation rule: relations in, coordinates out. A language model is worst at one-shot absolute geometry and best at relations ("the cap hugs the codec's supply pins", "USB-C sits at the contract's port"). scripts/pcblib/ keeps the relations as code and computes the millimetres:

from pcblib import (load_constraints, load_parts, Board, Cluster, place,
                    beside, align_pads, row, at_edge, scorecard,
                    export_placement, wire, via, gnd_pours)
C, P = load_constraints("../../cad/constraints.yaml"), load_parts("../parts.yaml")
brd = Board(pcb, C)                     # outline/holes/keepouts FROM the contract
PWR = Cluster(brd, "PWR", (55, 25))     # cluster origins: the only tuned numbers
u5 = PWR.place("Package_TO_SOT_SMD", "SOT-223-3_TabPin2", "U5",
               value=P["U5"].value, nets=P.netmap("U5"))
beside(u5, c4, side="right", gap=0.7)   # positions computed off real courtyards
at_edge(brd, j1, "usb_c")               # x/y comes from constraints.yaml, not a literal
fails = scorecard(brd, budgets={"hpwl_mm": 2000})   # hard gates BEFORE copper
export_placement(brd, "../placement.json", kinds={...})  # evidence for plm/cad

Read the full file on GitHub · 226 lines

Files

What ships with it

25 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.

Changes

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.

7d ago First seen · 226 lines · 353 tokens per session scan A 5d82c457aa55

Subscribe to this mod's changes

vibe-pcb is a skill published in the GitHub repository luckiday/vibe-hardware (5 stars, last pushed 15d ago), licensed MIT. It adds 353 tokens to every session and 3,605 once invoked, about $0.0018 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.

Hardware and IoT

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

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.

NVIDIA/skills · 50 tokens