easyeda-mcp-pro: Skill for Claude Code

.opencode/skills/component-search/SKILL.md

component-search is a skill for Claude Code, OpenCode from oaslananka/easyeda-mcp-pro. It costs 32 tokens per session (1,038 once invoked), scanned A, original, MIT.

A workflow for finding electronic parts in EasyEDA, a tool for designing circuit boards, and checking how they fit a bill of materials (BOM), the list of parts needed to build a device.

In plain words
What is it for?
Use it to search schematic components, review or prepare a BOM, compare suppliers such as LCSC or JLCPCB, and assess part quality and production risks.
Why use it?
It helps reduce the risk of choosing parts that do not meet the design requirements or are difficult to source. It also organizes supplier, price, availability, and production-risk checks when the relevant data is available.

Skill for Claude CodeOpenCode

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

This is oaslananka/easyeda-mcp-pro's own configuration. It tells Claude Code and OpenCode how to work on easyeda-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 easyeda-mcp-pro configures →

Part of the easyeda-pro plugin — 4 skills, 1 MCP server shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to oaslananka/easyeda-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/easyeda-mcp-pro/main/.opencode/skills/component-search/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/oaslananka/easyeda-mcp-pro

Made for: Claude Code, OpenCode.

Or install easyeda-pro, the plugin that ships this one along with the rest of its 4 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 component-search

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/oaslananka/easyeda-mcp-pro/component-search"><img src="https://agentmods.dev/badge/skills/oaslananka/easyeda-mcp-pro/component-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,038 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.00032 $0.01038
Opus 5 $0.00016 $0.00519
Sonnet 5 $0.00006 $0.00208
Haiku 4.5 $0.00003 $0.00104

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

Security

Grade A, and why

component-search 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.

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/component-search/SKILL.md · 128 lines

How it starts

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

Component Search Skill

Use this skill when an AI agent is asked to find, review, source, compare, or validate components for an EasyEDA Pro project through EasyEDA MCP Pro.

This skill is specific to oaslananka/easyeda-mcp-pro and must stay aligned with the registered MCP tools in src/tools/ and the tool list in README.md.

When to use

Use this skill for:

  • EasyEDA schematic device search
  • BOM generation and review
  • LCSC/JLCPCB-oriented sourcing checks
  • Supplier pricing and availability review
  • BOM export preparation
  • Component-quality and production-risk reporting

Do not use this skill to promise live inventory, price, lifecycle, or compliance facts unless the relevant tool result actually provides them.

Required context

Collect:

  • Target component requirements: value, tolerance, package, voltage, current, temperature, lifecycle, and manufacturer constraints
  • Preferred supplier or marketplace: LCSC, JLCPCB, DigiKey, Mouser, or project default
  • Assembly target: prototype, JLCPCB assembly, manual assembly, or production
  • Active schematic and BOM state
  • Whether component placement or property updates are allowed
  • API credentials or supplier integration status when supplier tools require them

Primary MCP tools

Schematic and component discovery

  • easyeda_schematic_components
  • easyeda_schematic_search_device
  • easyeda_schematic_component_pins
  • easyeda_schematic_net_detail
  • easyeda_schematic_nets

LCSC catalog verification and caching

  • easyeda_catalog_verify_device — resolve an LCSC part number into a catalog device entry (keyless LCSC metadata plus an EasyEDA symbol/footprint reference if already known locally) and cache it locally; use before recommending a generic/unresolved part by its LCSC number
  • easyeda_catalog_list — list devices already cached by easyeda_catalog_verify_device, filterable by resolved/partial/unresolved status; check this before re-verifying a part that may already be cached

BOM generation and validation

Read the full file on GitHub · 128 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. 10d ago First seen · 128 lines · 32 tokens per session scan A b8a553334b33

Subscribe to this mod's changes

component-search is a skill published in the GitHub repository oaslananka/easyeda-mcp-pro (45 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 1,038 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.