A PCB design checker for boards open in EasyEDA Pro. It runs many hygiene checks on schematics and board layouts, then creates a report and a JSON copy of the results.

It is for checking circuit schematics and PCB layouts, such as power connections, voltage-divider choices, and spacing near the board edge. It can run all checks or only schematic checks.

It catches common design mistakes before a board is manufactured, while making clear that it does not replace datasheet review or the manufacturer's own checks.

pcb-lint — Skill for Claude Code and Codex by sheares/easyeda-mcp-fix

Install

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.

Any agent

npx skills add sheares/easyeda-mcp-fix --skill pcb-lint

Clone the repo

git clone --depth 1 https://github.com/sheares/easyeda-mcp-fix

Made for: Claude Code, Codex.

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/skills/sheares/easyeda-mcp-fix/pcb-lint/github.svg)](https://agentmods.dev/skills/sheares/easyeda-mcp-fix/pcb-lint)

Your own site

<a href="https://agentmods.dev/skills/sheares/easyeda-mcp-fix/pcb-lint"><img src="https://agentmods.dev/badge/skills/sheares/easyeda-mcp-fix/pcb-lint/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/skills/sheares/easyeda-mcp-fix/pcb-lint"><img src="https://agentmods.dev/badge/skills/sheares/easyeda-mcp-fix/pcb-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,303 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.00108	$0.06303
Opus 5.5	$0.00043	$0.02521
Sonnet 5.5	$0.00022	$0.01261
Haiku 4.5	$0.00011	$0.00630

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

Security

Grade A, and why

pcb-lint 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 10d ago.

The scan reads SKILL.md. This mod also ships 56 executable files (scripts/checks/__init__.py, scripts/checks/base.py, scripts/checks/pcb_01_drc.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/pcb-lint/SKILL.md · 290 lines

How it starts

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

pcb-lint

A structured design-hygiene pass over the board open in EasyEDA Pro. You (Claude) call the mcp__easyeda__* tools directly, apply the check rules below, and write a markdown report plus a JSON sidecar.

It is a second pair of eyes, not a sign-off. It catches the common, expensive mistakes (an overvoltage regulator divider, a USB-C port that never gets power, copper too close to the board edge) before you pay for boards. It does not replace reading the datasheets or the fab's own DRC.

What is in this folder

SKILL.md (this file): the operational rules you follow.
scripts/checks/{sch,pcb}_*.py: a Python reference implementation of 25 of the 26 checks, unit-tested against mock MCP payloads (tests/, 189 tests). When a rule below is ambiguous, read the Python. If the Python and this file disagree, the Python is the truth.
scripts/config.example.json: a template for the optional per-board config.

The Python is a test harness and reference, not the runner. You are the runner.

Invocation modes

/pcb-lint (no arguments): run all checks and assemble one report grouped by severity. The normal path.
/pcb-lint sch: schematic checks only (SCH-*). Use when the schematic exists but the PCB is not laid out yet.
/pcb-lint pcb: PCB checks only (PCB-*).
/pcb-lint <check-id> (for example /pcb-lint PCB-21): one check only. Use to iterate quickly while fixing one class of finding.

Preconditions

EasyEDA Pro is running with the target project open.
The bridge is live. Call mcp__easyeda__server_info first. If the call fails, or extensionConnected is false, or connectedInstanceCount is 0, tell the user the extension is not connected (in EasyEDA Pro: Claude → Connect Claude in the top menu) and stop. Do not run checks against a dead bridge.
The right board is active. Call mcp__easyeda__editor_get_open_tabs and confirm the active tab is the board the user means. If several EasyEDA windows are open, use mcp__easyeda__list_instances and pass the right instance_id.
Config file (optional). Look for pcb-lint.config.json in the project folder the user is working from. If absent, run with defaults and emit a CONFIG-01 info finding pointing at scripts/config.example.json.

Read the full file on GitHub · 290 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

10d ago First seen · 290 lines · 108 tokens per session scan A d5077c4163d4

Subscribe to this mod's changes

pcb-lint is a skill published in the GitHub repository sheares/easyeda-mcp-fix (0 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 6,303 once invoked, about $0.0004 per session on Opus 5.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-10-05.

Claude Code Hardware and IoT Testing Unit testing anthropic claude easyeda easyeda-pro eda

pcb-lint

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

pcb-lint

What is in this folder

Invocation modes

Preconditions

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

tdd-workflow

rust-testing

cpp-testing

golang-testing

swift-protocol-di-testing

web3-testing