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.
npx skills add nickkraakman/skidl-skills --skill design-reviewgit clone --depth 1 https://github.com/nickkraakman/skidl-skillsWrote 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/skills/nickkraakman/skidl-skills/design-review)<a href="https://agentmods.dev/skills/nickkraakman/skidl-skills/design-review"><img src="https://agentmods.dev/badge/skills/nickkraakman/skidl-skills/design-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/skills/nickkraakman/skidl-skills/design-review"><img src="https://agentmods.dev/badge/skills/nickkraakman/skidl-skills/design-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.00096 | $0.00865 |
| Opus 5 | $0.00048 | $0.00432 |
| Sonnet 5 | $0.00019 | $0.00173 |
| Haiku 4.5 | $0.00010 | $0.00086 |
Grade A, and why
design-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 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review
When to use
- Before exporting a netlist or generating a BOM
- After skidl-coder finishes a circuit
- User says "review the circuit", "design review", or "check the design"
- Invoked via
/skidl-ee:design-review [circuit_name]
Inputs
circuits/<circuit_name>.py— SKiDL sourceSPEC.md— captured design requirementsarchitecture/folder (if present) — block diagram and net planpipeline_state.json— current pipeline status
Procedure
Run these three checks (in parallel where possible):
1. Electrical Rules (ERC)
- Spawn the
erc-revieweragent (it applies the erc-rules skill automatically) - Receive
erc_report.mdwith pass/fail verdict
2. Architecture Sanity
- Re-read
SPEC.mdandarchitecture/folder - Check:
- All functional blocks present in the circuit?
- Power budget realistic?
- Net plan complete and consistent with code?
- Known design risks (decoupling, protection, EMI) addressed?
3. SKiDL Code Quality
- Read current
circuits/*.pyfile(s) - Verify using the
.claude/rules/skidl-syntax.mdrules:- Every part has
ref,value, andfootprint? @subcircuitused for repeated blocks?- Decoupling caps named
C_DECOUP_*? NCon all intentionally unused pins?- Net naming: UPPERCASE power rails, camelCase signals?
ERC()call present in__main__?
- Every part has
4. Footprint Validation
- Run:
python3 .claude/scripts/validate-footprints.py circuits/<circuit_name>/(or.pyfor monolithic) - Every missing footprint is a HIGH severity finding — it will cause KiCad import errors
- For each missing footprint in the report:
- If the script suggests close matches → recommend the corrected string
- If no standard library match exists → generate a custom footprint:
- Read the datasheet mechanical drawing from
datasheets/<MPN>_SUMMARY.mdor PDF - Run
.claude/scripts/generate-footprint.pywith pad positions and sizes - Update the circuit code to reference
ProjectLocal:FootprintName
- Read the datasheet mechanical drawing from
- Do not mark review complete until footprint validation exits 0
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 · 90 lines · 96 tokens per session scan A 5fb9fd589289
design-review is a skill published in the GitHub repository nickkraakman/skidl-skills (18 stars, last pushed 5mo ago), licensed MIT. It adds 96 tokens to every session and 865 once invoked, about $0.0005 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 skills, from other repositories
kicad-pcb-review
Use this skill when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.
arch-review
Read-only architecture review of RTL vs uArch spec with area/timing/power tradeoffs. Use for post-RTL architecture sign-off or suspected spec mismatch.
rtl-review
Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.
cdc-tool-profiles
Internal reference: cdc tool profiles (agent-loaded; do not invoke).
kicad-pcb-review
KiCad PCB review and manufacturing readiness agent skill for Cursor.
argos-upload
Upload a screenshot, an image or a screen recording to Argos and get a shareable URL plus ready-to-paste Markdown, so it can be embedded in a pull request, an issue, a changelog or a chat message — or attached to a branch or pull request, where Argos posts and maintains the comment itself. Use whenever you have…