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 nrl-ai/chub --skill electronics-sourcinggit clone --depth 1 https://github.com/nrl-ai/chubWrote 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/nrl-ai/chub/electronics-sourcing)<a href="https://agentmods.dev/skills/nrl-ai/chub/electronics-sourcing"><img src="https://agentmods.dev/badge/skills/nrl-ai/chub/electronics-sourcing.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.00027 | $0.01628 |
| Opus 5 | $0.00014 | $0.00814 |
| Sonnet 5 | $0.00005 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
electronics-sourcing 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.
This is a copy
100% identical to electronics-sourcing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electronics Sourcing Skill
This skill teaches you how to source electronic components effectively using parts-mcp tools. It covers tool sequencing, decision patterns, and how to handle common scenarios.
When to Use Which Search Tool
search_parts — Use when you have a part number, description, or general keywords. This is your default starting point.
"Find me a 100nF capacitor" → search_parts(query="100nF capacitor")
"Look up STM32F411" → search_parts(query="STM32F411")
search_by_parameters — Use when you need to match specific electrical parameters within a category. More precise than keyword search.
"I need a 50V 100nF X7R 0402 cap" → search_by_parameters(
parameters={"capacitance": "100nF", "voltage": "50V", "dielectric": "X7R", "package": "0402"},
category="capacitor"
)
Decision rule: If the user gives you 3+ specific parameters, use search_by_parameters. For part numbers or general queries, use search_parts.
The Search → Price → Availability → Alternative Pattern
This is the core sourcing workflow. Follow this sequence:
1. SEARCH → Find the part
2. DETAILS → Get full specifications (if needed for validation)
3. PRICE → Compare across suppliers
4. AVAILABILITY → Check stock levels
5. ALTERNATIVE → Find replacements (only if price is too high or stock is insufficient)
Do not skip steps 3 and 4. A part that exists in the database may be out of stock or prohibitively expensive.
When the user asks to "source" or "find" a part, they expect pricing and availability — not just search results. Always follow through to at least step 4.
BOM Processing Pattern
BOM processing is asynchronous. Always follow this exact sequence:
1. upload_bom(file_path=path) → Get job_id
2. check_bom_status(job_id=job_id) → Poll until status is "complete"
3. Review matched_parts and unknown_parts
4. For unmatched: search_parts() to resolve manually
5. calculate_bom_cost() with all resolved parts
Polling: Call check_bom_status and check the status field. If "in_progress", wait and poll again. Do not assume instant completion.
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 · 166 lines · 27 tokens per session scan A ca56883c65b7
electronics-sourcing is a skill published in the GitHub repository nrl-ai/chub (11 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 1,628 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to electronics-sourcing, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
Embedded C/C++ rules for MCU, STM32, HAL, interrupts, DMA, memory constraints, a
Embedded C/C++ rules for MCU, STM32, HAL, interrupts, DMA, memory constraints, and hardware-focused testing.
bitcoin-hardware-trezor
Trezor hardware wallets: Model T, Model One, Trezor Safe 3, Safe 5. Trezor Suite, trezorctl, USB protocol, BIP32 derivation, passphrase support, Shamir Backup. USE WHEN: integrating with Trezor, supporting Trezor in app, troubleshooting Trezor signing.
bitcoin-hardware-coldcard
Coldcard hardware wallets (Coinkite): Mk4, Q. Bitcoin-only firmware, airgap support via SD card / NFC / QR, BIP85, MuSig2 (experimental), Trick PINs. USE WHEN: integrating with Coldcard, supporting Mk4 / Q, designing airgap signing flows.
dos-goal-gate
Ground a keep-working goal in evidence the worker did not author by wiring dos hook stop to refuse false done claims. Use for one self-stopping agent or loop worker; use dos-witness-claim for fold barriers.
dos-witness-claim
Route subagent claims through independent read-back before another agent relies on them. Use at parallel, pipeline, or synthesis barriers where shipped phases, files, rows, messages, or other effects must be witnessed.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.