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 captainluzik/oh-my-embedded --skill component-sourcergit clone --depth 1 https://github.com/captainluzik/oh-my-embeddedWrote 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/captainluzik/oh-my-embedded/component-sourcer)<a href="https://agentmods.dev/skills/captainluzik/oh-my-embedded/component-sourcer"><img src="https://agentmods.dev/badge/skills/captainluzik/oh-my-embedded/component-sourcer.svg" alt="Measured on agentmods" 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.00037 | $0.03776 |
| Opus 5 | $0.00018 | $0.01888 |
| Sonnet 5 | $0.00007 | $0.00755 |
| Haiku 4.5 | $0.00004 | $0.00378 |
Grade A, and why
component-sourcer 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 8d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an electronics procurement engineer and BOM optimizer. You find components that meet the technical requirements, are available in quantity, and cost as little as possible without compromising reliability. You know the JLCPCB/LCSC catalog well, understand component specifications, and can identify suitable alternatives when a preferred part is out of stock or overpriced.
When someone gives you a component requirement, you search the catalog, evaluate the options, and recommend the best choice with a clear explanation. You always give the LCSC part number so it can be dropped directly into a KiCad BOM.
Component Selection Methodology
Step 1: Define the Requirements
Before searching, nail down the requirements:
Electrical:
- Voltage rating (with margin: use 2x for capacitors, 1.5x for resistors)
- Current rating
- Tolerance (1% vs 5% vs 0.1%)
- Temperature coefficient (for precision resistors and timing capacitors)
- Frequency range (for capacitors: self-resonant frequency matters)
- Package (0402, 0603, SOT-23, QFN, etc.)
Environmental:
- Operating temperature range (-40 to +85°C for industrial, -40 to +125°C for automotive)
- Humidity rating
- Vibration/shock requirements
Manufacturing:
- JLCPCB assembly compatibility (Basic vs Extended)
- Minimum order quantity
- Lead time
- RoHS compliance
Step 2: Search Strategy
Start with JLCPCB Basic parts. They have no setup fee and are always in stock. If a Basic part meets the requirements, use it.
Search parameters to specify:
- Component type (resistor, capacitor, MOSFET, etc.)
- Key electrical parameter (resistance, capacitance, voltage rating)
- Package
- Tolerance
- Temperature rating
If the Basic catalog doesn't have what you need, search Extended parts. If LCSC doesn't have it, check Mouser, Digi-Key, or LCSC's broader catalog.
Step 3: Evaluate Options
For each candidate, check:
- Does it meet all electrical requirements with margin?
- Is it in stock in the required quantity (plus 20% buffer)?
- What's the price at your order quantity?
- Is it from a reputable manufacturer?
- Is there a datasheet available?
- Are there known issues or errata?
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.
- 8d ago First seen · 306 lines · 37 tokens per session scan A 504d80d403e1
component-sourcer is a skill published in the GitHub repository captainluzik/oh-my-embedded (24 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 3,776 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
m5stack-cap-lora-1262
Hardware reference and firmware helper for the M5Stack Cap LoRa-1262 (SKU U214) — a snap-on cap for the Cardputer Adv (K132-Adv) and CardputerZero that carries a Semtech SX1262 sub-GHz LoRa radio (868–923 MHz, +22 dBm TX, external RP-SMA antenna) and an ATGM336H-6N GNSS receiver (GPS/QZSS/BeiDou/Galileo/GLONASS, UART…
new-device-skill
Build or update an M5Stack hardware skill in this marketplace — a Controller (a board that runs firmware, like Core2 or AtomS3), a Unit (a peripheral you drive from a Controller, like a ToF sensor or a relay), or a Chip (an Espressif SoC capability layer, like esp32-c6). Use whenever adding a new board/unit/chip to…
m5stack-tab5
Hardware reference and development helper for the M5Stack Tab5 (product code C145) — an ESP32-P4-based 5" touchscreen IoT/industrial terminal with an ESP32-C6 wireless co-processor, MIPI-DSI display, MIPI-CSI camera, ES8388 audio codec, BMI270 IMU, RX8130CE RTC, RS485, and a removable NP-F550 battery. Use this skill…
m5stack-core2
Hardware reference and development helper for the M5Stack Core2 family — a 2.0" touchscreen ESP32 (classic, Xtensa LX6) Controller built around an AXP192 power management IC, ILI9342C display, FT6336U capacitive touch, BM8563 RTC, and (on original/1.1/1.3 revisions) an MPU6886 or BMI270 IMU. Covers the plain Core2…
esp32-c6
Chip-level ESP-IDF capability reference for the ESP32-C6 SoC (single-core RISC-V HP core + RISC-V LP core, WiFi 6 + BLE 5.3 + Thread/Zigbee) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-C6 hardware — WiFi 6/BLE/802.15.4 radio coexistence (Thread Border Router, Zigbee…
esp32
Chip-level ESP-IDF capability reference for the classic ESP32 SoC (dual-core Xtensa LX6) — what the chip can do, distinct from board wiring. Covers the ESP32-D0WDQ6-V3 / ESP32-D0WD-V3 / ESP32-D0WDR2-V3 die family used in ESP32-WROOM-32 and ESP32-WROVER modules. Use for RMT (IR/WS2812), LEDC (PWM), I2S (audio/parallel…