What is board-recipe-scaffold?

A template generator for consumer printed-circuit-board recipes. It creates a nine-step project-to-manufacturing pipeline covering the schematic, electrical checks, board layout, routing, verification, and export, while leaving circuit-specific details blank.

Use it to start a new board-generation script, organize the design and verification stages, identify circuit-specific fill-in points, and produce the board and manufacturing files.

It provides a repeatable starting structure without pretending to know the design of a particular board. The committed board file remains the version intended for manufacturing even if later regeneration differs.

How rjwalters/kicad-tools configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rjwalters/kicad-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/kct/board-recipe-scaffold.md

Clone the repo

git clone --depth 1 https://github.com/rjwalters/kicad-tools

Made for: Claude Code.

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/commands/rjwalters/kicad-tools/board-recipe-scaffold/github.svg)](https://agentmods.dev/commands/rjwalters/kicad-tools/board-recipe-scaffold)

Your own site

<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/board-recipe-scaffold"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/board-recipe-scaffold/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/board-recipe-scaffold"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/board-recipe-scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,199 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.00056	$0.03199
Opus 5	$0.00028	$0.01599
Sonnet 5	$0.00011	$0.00640
Haiku 4.5	$0.00006	$0.00320

Measured 11d ago against content hash 0e013e309f91, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

board-recipe-scaffold 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 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.

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.

.claude/commands/kct/board-recipe-scaffold.md · 154 lines

How it starts

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

Board recipe scaffold

Scaffold a new generate_design.py-style board recipe for a consumer PCB, following the artifact-first convention: the committed board artifact is shipping truth, and regeneration may diverge by design. This skill emits the proven sequential pipeline (steps 1-9) as a template with the circuit-specific parts left as clearly marked fill-in points — it does not reproduce any specific board's circuit.

The kct namespace. This skill lives in .claude/commands/kct/ — the kicad-tools-native, harness-agnostic agent-tool namespace, invoked as /kct:board-recipe-scaffold. It runs from inside a consumer repo that depends on kicad-tools as a uv dependency. It hardcodes no board path and assumes nothing about the current directory being the kicad-tools repo.

Artifact-first (why this shape). The recipe's job is to generate a board artifact; once committed, that artifact is the shipping truth. A later python generate_design.py run may diverge from the committed artifact (placement heuristics, router seed) — that is intentional, not a bug. The committed *.kicad_pcb and its manufacturing/ bundle are what ships; the recipe documents how it was produced. This is Epic #4054 convention #3 expressed as code structure.

Prerequisite

The native router/DRC backend must be built in the active checkout before the routing step (step 5) will run at full speed (Epic #4054 convention #1):

uv run kct build-native --check   # expect: "C++ backend: available"
uv run kct build-native           # if "not installed" (uv sync does NOT build it)

Model selection

suggestedModel: sonnet. Emitting a well-understood pipeline template with marked fill-in points is a structured code-generation task, not a frontier-judgment one. Model resolves through the harness's normal precedence chain.

Arguments

Arguments: $ARGUMENTS

$ARGUMENTS is <board-path> [--name <slug>] [--mfr <tier>].

Token	Meaning
`<board-path>`	Required. The directory for the new board recipe (e.g. the path where `generate_design.py` and its `output/` will live). The user supplies it; the scaffold writes into it. Never a hardcoded board directory.
`--name <slug>`	Project slug used for the `.kicad_pro` / output filenames. Optional; default derived from `<board-path>`'s basename.
`--mfr <tier>`	Fab tier for the export step. Optional; if omitted, leave a marked fill-in point and resolve it the same way `/kct:manufacturing-readiness` does (read the recipe/manifest or ask the user; validate against `kicad_tools.manufacturers.get_manufacturer_ids()` / `kct export --help`). Do not hardcode a tier list.

Read the full file on GitHub · 154 lines

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.

11d ago First seen · 154 lines · 56 tokens per session scan A 0e013e309f91

Subscribe to this mod's changes

board-recipe-scaffold is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 3,199 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-30.

Hardware and IoT

kicad-tools: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Board recipe scaffold

Prerequisite

Model selection

Arguments

What this file has done since we first saw it

Other commands, from other repositories

eol-report

cisco-catalyst-ta-setup

rvcsi-calibrate

esp-harden

pentest-wireless

put