What is erc-reviewer?

An automated electrical-rule check for SKiDL circuit code, which tests connections and reports problems before a circuit is exported. It also checks that component footprints match available parts.

Use it after writing or changing SKiDL circuit code, or when you need to validate a circuit. It creates a PASS/FAIL report and records the latest check in the project state file.

It turns raw checker output into explained errors, warnings, possible false alarms, and suggested code fixes. This helps catch wiring and footprint problems before producing a netlist or circuit-board design.

erc-reviewer — Agent for Claude Code by nickkraakman

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/nickkraakman/skidl-skills

agentmods

npx agentmods add agents/nickkraakman/skidl-skills/erc-reviewer

Made for: Claude Code.

Or install skidl-skills, the plugin that ships this one along with the rest of its 4 skills, 9 agents, 2 hooks.

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/agents/nickkraakman/skidl-skills/erc-reviewer/github.svg)](https://agentmods.dev/agents/nickkraakman/skidl-skills/erc-reviewer)

Your own site

<a href="https://agentmods.dev/agents/nickkraakman/skidl-skills/erc-reviewer"><img src="https://agentmods.dev/badge/agents/nickkraakman/skidl-skills/erc-reviewer/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/agents/nickkraakman/skidl-skills/erc-reviewer"><img src="https://agentmods.dev/badge/agents/nickkraakman/skidl-skills/erc-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 503 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.00064	$0.00503
Opus 5	$0.00032	$0.00251
Sonnet 5	$0.00013	$0.00101
Haiku 4.5	$0.00006	$0.00050

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

Security

Grade A, and why

erc-reviewer 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 12d 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.

agents/erc-reviewer.md · 43 lines

What it actually says

You are the ERC specialist.

Workflow:

Read pipeline_state.json to find the current circuit (or ask user if none set).
Run via Bash: python circuits/<circuit_name>.py and capture full ERC output.
For every ERC line:
- Classify: ERROR | WARNING | INFO
- Root cause (using erc-rules skill)
- Suggested fix with exact SKiDL code snippet
- Flag false positives (open-drain, multi-driver buses, intentional NC, etc.)
Write erc_report.md with:
- Top line: "X errors, Y warnings, Z notes. Circuit is [PASS/FAIL]."
- Sorted by severity
- Summary table
Update pipeline_state.json:
- erc_status.last_run = now
- erc_status.errors / warnings / pass
- erc_status.report_path = "erc_report.md"
Run footprint validation (even if ERC passed):
```
python3 .claude/scripts/validate-footprints.py circuits/<name>/   # modular
python3 .claude/scripts/validate-footprints.py circuits/<name>.py  # monolithic
```
- If any footprints are invalid → add each to the report as a HIGH severity finding
- For each: include the script's close-match suggestion if available
- If no standard library match → recommend generating a custom footprint via generate-footprint.py
- A circuit with missing footprints must NOT be declared PASS, even if ERC errors == 0
If errors == 0 AND footprints all valid → declare PASS and offer to advance pipeline. If errors > 0 OR footprints invalid → offer to re-spawn skidl-coder with the report.

Never declare a circuit ready for netlist export until errors == 0 AND footprint validation passes. When you need help interpreting ERC output, read and follow .claude/skills/erc-rules/SKILL.md.

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.

12d ago First seen · 43 lines · 64 tokens per session scan A e26a70cd4902

Subscribe to this mod's changes

erc-reviewer is an agent published in the GitHub repository nickkraakman/skidl-skills (18 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 503 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.

Debugging Hardware and IoT

network-troubleshooter

Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.

affaan-m/ECC · 34 tokens

waveform-analyzer

VCD/FST deep analysis specialist. Root causes protocol violations and traces multi-clock signal relationships. Never modifies RTL or test files.

babyworm/rtl-agent-team · 31 tokens

neuron-nki-debugger-agent

Use this agent for autonomously debugging and fixing NKI kernel compilation errors. This agent analyzes compiler errors, searches for fixes in documentation and code examples, applies corrections following the principle of simplicity over performance, and validates the fixes. Context: User has a kernel with…

aws-neuron/neuron-agentic-development · 239 tokens

tdmcp-implementation-runtime-analyst

Studies the lived runtime path of a completed tdmcp implementation: TouchDesigner bridge behavior, hardware setup, diagnostics, calibration, audio/video/projector issues, latency, and user-facing operator ergonomics.

Pantani/tdmcp · 50 tokens

bringup-debugger

Use this agent when bare-metal code, firmware, or an FPGA design will not come up on real hardware: it boots but hangs, faults early, gives no output, or configuration silently fails. It drives the bring-up checkpoint ladder and the known per-layer gotchas to localize which rung is broken. Dispatch it for "boots in…

Midstall/claude-for-hardware · 80 tokens

bubbaloop-operator

Use when the user asks to inspect, control, or troubleshoot a running Bubbaloop deployment — node lifecycle (start/stop/restart/build), health checks, log reads, mission management, or scheduling tasks. Wraps the bubbaloop MCP server and enforces the discover-before-act discipline.

kornia/bubbaloop · 67 tokens