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.
curl -O https://raw.githubusercontent.com/oaslananka/easyeda-mcp-pro/main/.opencode/skills/component-search/SKILL.mdgit clone --depth 1 https://github.com/oaslananka/easyeda-mcp-proWrote 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/oaslananka/easyeda-mcp-pro/component-search)<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.
<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>- NVIDIA SkillSpector pass
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.00032 | $0.01038 |
| Opus 5 | $0.00016 | $0.00519 |
| Sonnet 5 | $0.00006 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
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.
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_componentseasyeda_schematic_search_deviceeasyeda_schematic_component_pinseasyeda_schematic_net_detaileasyeda_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 numbereasyeda_catalog_list— list devices already cached byeasyeda_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
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 · 128 lines · 32 tokens per session scan A b8a553334b33
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.
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.
kicad-pcb-review
KiCad PCB review and manufacturing readiness agent skill for Cursor.
easyeda-agent
An automation skill for EasyEDA Pro, a tool used to design electronic schematics and printed circuit boards.
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.
omh-physical-device-readiness
This is a Hermes-native physical-device-readiness workflow skill.
kicad
Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label…