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/ee-review.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/ee-review)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/ee-review"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/ee-review/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/ee-review"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/ee-review.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.00033 | $0.04584 |
| Opus 5 | $0.00016 | $0.02292 |
| Sonnet 5 | $0.00007 | $0.00917 |
| Haiku 4.5 | $0.00003 | $0.00458 |
Grade A, and why
ee-review 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EE Review
Produce an EE decision document for an analog/placement-blocked board — an escalating intervention ladder plus binding electrical constraints, cited and confidence-graded — so a builder can execute the fix artifact-first without waiting on the owner's calendar.
The
kctnamespace. This skill lives in.claude/commands/kct/— the kicad-tools-native agent-tool namespace, invoked as/kct:ee-review. Keep kicad-tools' own agent tools here, not under.claude/commands/loom/or.loom/roles/: that tree is installed into this repo from rjwalters/loom and belongs to the loom framework. Thekctnamespace is deliberately harness-agnostic — it hosts kicad-tools-native skills that live alongside installable harness frameworks (loom, rjwalters/anvil, or any future orchestrator). Future kicad-tools skills should follow this convention: kicad-tools-native tools go under.claude/commands/kct/.
Scope (advisory only). This skill produces decisions, not copper. It reads the board artifact, the
kct net-status --whyclassification, the issue thread, and published/textbook/app-note evidence, then writes a single decision document (one issue comment in issue mode, or one<board>/EE_REVIEW.mdin board mode). It never routes copper, never places parts, never edits the.kicad_pcb, and never self-applies a work label. The human approval gate is preserved: the owner ratifies the ladder + constraints before any builder executes them. Execution is the existing artifact-first builder pipeline's job, referee-gated bykicad-cli pcb drc --refill-zones.Phase 1 (this doc) is a single opus-class reviewer. It reads the inputs and writes the decision document directly. The Phase-2 research fan-out (4 sonnet researchers → opus planner) is documented here as the two protocols below, but Phase 1 does not spawn subagents and does not exercise the live paper-request / feature-request paths against paywalled sources.
--depth mvpis the implicit default and the only supported mode in Phase 1.
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 · 182 lines · 33 tokens per session scan A 9f48448559be
ee-review is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 4,584 once invoked, about $0.0002 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
gpu
Diagnose GPU health, discover bounded recipes, and collect typed numeric evidence without guessing from screenshots.
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
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.
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.
verify
An embedded-device verification workflow that checks a development step through building, flashing firmware, debugging with J-Link, and reading serial logs. Firmware is software that runs directly on a microcontroller or other device.
log
Analyze captured serial logs for key events.