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.
git clone --depth 1 https://github.com/Midstall/claude-for-hardwareWrote 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/midstall/claude-for-hardware/tapeout-check)<a href="https://agentmods.dev/commands/midstall/claude-for-hardware/tapeout-check"><img src="https://agentmods.dev/badge/commands/midstall/claude-for-hardware/tapeout-check/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/midstall/claude-for-hardware/tapeout-check"><img src="https://agentmods.dev/badge/commands/midstall/claude-for-hardware/tapeout-check.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.00012 | $0.00287 |
| Opus 5 | $0.00006 | $0.00143 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
tapeout-check 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 9d 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.
What it actually says
The user is preparing a design for tapeout or an MPW shuttle. Context: $ARGUMENTS
Invoke the tapeout-precheck skill (and silicon-grade-discipline for the failures-should-fail stance). Then walk the signoff gate honestly, in order:
- DRC: read the actual report and confirm zero unwaived violations. Do not infer clean from an absent error message or a run that skipped the rule deck.
- LVS: confirm the extracted netlist matches the source exactly, no shorts, opens, or unintended merges.
- Density and fill satisfied without introducing new violations.
- Submission package: top-cell name, layer map, metadata, and file format correct for this foundry or shuttle.
Enforce the hard rules: a failing check means fix the design, never disable the checker; never flatten and merge std-cell metal across cell boundaries; a legitimate waiver is foundry-granted in writing, not a flag flipped to hit a date.
If the user is asking whether they can suppress or wave a violation, the answer is to fix the design unless they have a written foundry waiver. Give a clear ready / not-ready verdict with blocking items and their design-side fixes.
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.
- 9d ago First seen · 18 lines · 12 tokens per session scan A 08e87bc49df6
tapeout-check is a command published in the GitHub repository Midstall/claude-for-hardware (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 287 once invoked, about $0.0001 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 commands, from other repositories
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
scope
A command for connecting to supported oscilloscopes, capturing or reading waveforms, measuring them, and saving results as CSV files or plots. An oscilloscope is a device that displays changing electrical signals.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.
svd
A command-line tool that reads CMSIS-SVD files, which describe a chip's peripherals, registers, and bit fields. It can list register addresses and decode the current register values while the device is running.
map
A parser for Keil compiler map files, which are build reports describing where program code and data are placed in memory. It reports object sizes, memory regions, symbols, and stack or heap details.
size
A command that reads a Keil compiler .map file, a build report describing where firmware uses memory. It reports Flash, RAM, stack, and heap allocation and compares usage with warning limits.