agentmods.dev

kicad-mcp-pro: Skill for Claude Code

.opencode/skills/drc-check/SKILL.md

drc-check is a skill for Claude Code, OpenCode from oaslananka/kicad-mcp-pro. It costs 26 tokens per session (1,020 once invoked), scanned A, original, MIT.

A workflow guide for checking KiCad schematics and circuit boards. ERC checks electrical connections in schematics, while DRC checks board layout against design rules.

In plain words
What is it for?
It helps run ERC and DRC checks, inspect rules, investigate unconnected nets and layout conflicts, review waivers, and revalidate edits.
Why use it?
It gives agents a structured way to find, assess, and recheck design problems without hiding violations without justification.

Skill for Claude CodeOpenCode

Written for Claude Code and OpenCode: shipped in a Claude Code plugin, but also installed under .opencode/.

This is oaslananka/kicad-mcp-pro's own configuration. It tells Claude Code and OpenCode how to work on kicad-mcp-pro itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kicad-mcp-pro configures →

Part of the kicad-pro plugin — 10 skills, 1 MCP server shipped together

not rated 83repo +19 today A scan SkillSpector: pass 26 tokens original MIT
View source ↗ oaslananka/kicad-mcp-pro oaslananka.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to oaslananka/kicad-mcp-pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/oaslananka/kicad-mcp-pro/main/.opencode/skills/drc-check/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/oaslananka/kicad-mcp-pro

Made for: Claude Code, OpenCode.

Or install kicad-pro, the plugin that ships this one along with the rest of its 10 skills, 1 MCP server.

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.

agentmods badge for drc-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/oaslananka/kicad-mcp-pro/drc-check/github.svg)](https://agentmods.dev/skills/oaslananka/kicad-mcp-pro/drc-check)
Your own site
<a href="https://agentmods.dev/skills/oaslananka/kicad-mcp-pro/drc-check"><img src="https://agentmods.dev/badge/skills/oaslananka/kicad-mcp-pro/drc-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.

agentmods 80×15 button for drc-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/oaslananka/kicad-mcp-pro/drc-check"><img src="https://agentmods.dev/badge/skills/oaslananka/kicad-mcp-pro/drc-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,020 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01020
Opus 5 $0.00013 $0.00510
Sonnet 5 $0.00005 $0.00204
Haiku 4.5 $0.00003 $0.00102

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

Security

Grade A, and why

drc-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 11d 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.

.opencode/skills/drc-check/SKILL.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DRC Check Skill

Use this skill when an AI agent is asked to run, interpret, triage, or revalidate KiCad ERC/DRC results through KiCad MCP Pro.

This skill is specific to oaslananka/kicad-mcp-pro and should be kept synchronized with docs/tools-reference.generated.md.

When to use

Use this skill for:

  • Schematic ERC review
  • PCB DRC review
  • DRC rule inspection and custom rule checks
  • Unconnected net triage
  • Courtyard and silk-to-pad violation triage
  • Waiver/exclusion review
  • Revalidation after an edit

Do not use this skill to hide, auto-waive, or normalize violations without explicit engineering rationale.

Required context

Collect:

  • Active project path and KiCad version from kicad_get_project_info
  • Board and schematic files
  • Target gate: ERC, DRC, project gate, release gate, or revalidation loop
  • Manufacturer or design-rule constraints, if relevant
  • Existing waivers/exclusions, if any

Primary MCP tools

Setup and discovery

  • kicad_get_project_info
  • kicad_get_version
  • kicad_help
  • kicad_get_tools_in_category

ERC and schematic checks

  • run_erc
  • erc_list_rules
  • schematic_quality_gate
  • schematic_connectivity_gate
  • schematic_design_rule_check
  • sch_check_power_flags
  • sch_get_net_names
  • sch_get_symbols

DRC and board checks

  • run_drc
  • drc_list_rules
  • drc_check_rule_conflicts
  • drc_list_exclusions
  • drc_validate_exclusions
  • get_unconnected_nets
  • get_courtyard_violations
  • get_silk_to_pad_violations
  • pcb_quality_gate
  • pcb_transfer_quality_gate
  • pcb_stackup_consistency_gate

Controlled rule/exclusion operations

Use these only when explicitly requested and when the rationale is documented.

  • drc_add_exclusion
  • drc_remove_exclusion
  • drc_rule_create
  • drc_rule_delete
  • drc_rule_enable
  • drc_export_rules
  • erc_set_rule_severity
  • erc_reset_rules

Project-level validation

  • project_quality_gate
  • project_quality_gate_report
  • project_full_validation_loop
  • project_revalidate_after_edit
  • project_gate_trend

Read the full file on GitHub · 153 lines

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.

  1. 11d ago First seen · 153 lines · 26 tokens per session scan A cb301dabffc8

Subscribe to this mod's changes

drc-check is a skill published in the GitHub repository oaslananka/kicad-mcp-pro (83 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,020 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.

Hardware and IoTTestingai-agentbomdfmdrcedaeda-automation
Related

Other skills, from other repositories

jlcpcb-headstage-pcb

A project-specific guide for reviewing and improving printed-circuit-board designs made for JLCPCB's electronics-manufacturing service. It also covers manufacturing files such as Gerbers and drill files.

Dissipative-ATLAS/jlceda-codex-mcp · 170 tokens

loop2converge

The closed convergence loop for ANY benchmark subject — open-benchmark Evaluation, benchmark IC (doc→GDS), or IP-cell (doc→LEF/GDS). RUN the canonical front door, CLASSIFY every FAIL as flow / gate / tool, CONVERGE it by fixing the layer that owns it, PROVE the fix in the plugin cache against the real artefacts BEFORE…

vibeic/vibe-ic · 237 tokens

phase1-coverage-loop

Closed-loop field-agent for Phase 1 coverage. Rotates through a benchmark IC folder (e.g. 2ndbanchmark/) running /vibe-ic-phase1 on each IC's README/prompt, measures input→L1-L27 token completeness with phase1inputvsgeneratedcompletenesscheck, and files chip-AGNOSTIC plugin backlog issues for systematic ingester gaps.…

vibeic/vibe-ic · 150 tokens

formal-verify

Run formal property verification (FPV) on RTL by driving model-checkers such as SymbiYosys, Jasper, or VC Formal. Use when the user says "prove this", "formal verify", "model check", "run sby", or has SVA properties from assertion-gen that need to be proven or bounded.

vibeic/vibe-ic · 71 tokens

phase2-rtl-verify

After designoneshotrunner emits RTL + SOF + reference TB PASS, AI spot-checks RTL quality and L9-contract conformance. Triggers when /vibe-ic-phase2 / /vibe-ic-phase2 returns PASS, or on phrases like "review the RTL", "check RTL quality", "verify phase 2 output".

vibeic/vibe-ic · 78 tokens

scope-pattern-attestation

Layer-3 hardware attestation — talk to an oscilloscope via SCPI to verify behavioral patterns (or absence of patterns) on real silicon IO. Use when sim and static RTL checkers can both pass but you need to confirm the actual hardware doesn't exhibit a forbidden timing pattern (e.g. periodic wake pulses that should…

vibeic/vibe-ic · 109 tokens