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.
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/kct/tapeout.mdgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/commands/rjwalters/kicad-tools/tapeout)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/tapeout"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/tapeout/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/commands/rjwalters/kicad-tools/tapeout"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/tapeout.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.00000 | $0.06983 |
| Opus 5.5 | $0.00000 | $0.02793 |
| Sonnet 5.5 | $0.00000 | $0.01397 |
| Haiku 4.5 | $0.00000 | $0.00698 |
Grade A, and why
tapeout 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 8d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tapeout
Produce a complete, orderable manufacturing package for a routed .kicad_pcb, or refuse and exit non-zero. This skill is the deliverable-completeness counterpart to sign-off: {{skill:manufacturing-readiness}} proves the copper is manufacturable; tapeout proves the package you are about to upload is complete and orderable.
The contract is exactly: tapeout returning 0 (with a manifest written) means "upload this output directory to the fab as-is." Anything less writes no manifest and exits non-zero, naming the gate that failed.
The
kctnamespace. This skill lives in{{skills-dir}}— the kicad-tools-native, harness-agnostic agent-tool namespace, invoked as{{skill:tapeout}}. It runs from inside a consumer repo that depends on kicad-tools as auvdependency (kct ...is onPATHvia the venv;kicad-clicomes from the KiCad install and is resolved as described below). It does not assume the current directory is the kicad-tools repo, and it hardcodes no board path, no fab-tier list, and no CI-workflow context.
Prerequisite
The native router/DRC backend must be built in the active checkout before this skill is meaningful (Epic #4054 convention #1). Run once per checkout / worktree:
uv run kct build-native --check # expect: "C++ backend: available"
# if "not installed":
uv run kct build-native
uv sync does not build the native extension. A fresh checkout or git worktree needs this step explicitly.
kicad-cli is required by both the mandatory DRC cross-gate (Gate 2, delegated) and the drawing-export gates (Gates 5–6), and jq by the pre-gates and Gate 4b. The venv does not provide kicad-cli, and a stock macOS install is not on PATH, so resolve it the way kct does — with the find_kicad_cli() one-liner from {{skill:manufacturing-readiness}} Gate 2 (it checks PATH, then the macOS app bundle, Homebrew and the Linux and Windows default install paths; kct doctor prints the path it found). Only an empty result means it is missing; then tapeout refuses (see Refusal conditions) — there is no partial-package fallback.
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.
- 8d ago Changed 6d1a398c9a9c
- 9d ago Changed · +8 lines f38576c8d923
- 21d ago Changed · +2 lines cc2706ced5b9
- 27d ago Changed b898269dbc19
- 1mo ago Changed a40fa5c269c1
- 1mo ago First seen · 227 lines · 0 tokens per session scan A 36f7d900fccd
tapeout is a command published in the GitHub repository rjwalters/kicad-tools (74 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,983 tokens. 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 commands, from other repositories
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
rvcsi-calibrate
Learn a v0 per-subcarrier baseline (mean amplitude) from a .rvcsi capture.
esp-harden
Harden and inspect ESP32 firmware for field failures, crashes, memory, and security.
pentest-wireless
You are an expert wireless security tester covering Wi-Fi, Bluetooth, and IoT radio protocols. For AUTHORIZED testing only.
device-info
A device-scanning command that identifies the connected chip and its VID:PID hardware identifiers. It also provides suggestions for the driver needed to use the device.
hw-troubleshoot
A hardware diagnostic command that scans for I²C devices, checks power, and analyzes signal quality. I²C is a short-distance communication bus used by many sensors and chips.