A guide for planning electronics bills of materials (BOMs), which list the parts needed to build a device, using DigiKey sourcing data.

It helps gather requirements, find candidate parts, check their details, validate a multi-part BOM, and prepare order lists with DigiKey and manufacturer part numbers. It does not place orders.

It helps avoid unsafe or unsupported part choices by requiring key electrical and manufacturing details and evidence before a part is considered ready to buy.

digikey-bom — Skill for Claude Code and Codex by itsyashk/digikey-mcp

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 itsyashk/digikey-mcp --skill digikey-bom

Clone the repo

git clone --depth 1 https://github.com/itsyashk/digikey-mcp

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/itsyashk/digikey-mcp/digikey-bom/github.svg)](https://agentmods.dev/skills/itsyashk/digikey-mcp/digikey-bom)

Your own site

<a href="https://agentmods.dev/skills/itsyashk/digikey-mcp/digikey-bom"><img src="https://agentmods.dev/badge/skills/itsyashk/digikey-mcp/digikey-bom/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/itsyashk/digikey-mcp/digikey-bom"><img src="https://agentmods.dev/badge/skills/itsyashk/digikey-mcp/digikey-bom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 700 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.00017	$0.00700
Opus 5.5	$0.00007	$0.00280
Sonnet 5.5	$0.00003	$0.00140
Haiku 4.5	$0.00002	$0.00070

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

Security

Grade A, and why

digikey-bom 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 2mo 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.

skills/digikey-bom/SKILL.md · 59 lines

How it starts

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

DigiKey BOM workflow

Use the digikey-mcp tools for read-only electronics sourcing. The system may search DigiKey and plan a BOM, but it never orders parts or changes an account. Do not place orders. Do not request or store credentials in chat.

Required behavior

Gather missing critical requirements before sourcing: voltage range, continuous and peak current, fault behavior, temperature/environment, interfaces, mating parts, package/footprint, polarity, lifecycle, assembly style, quantity, spares, and region.
Prefer digikey_build_electronics_bom for multi-part designs. Review its architecture and requirements ledger before discussing individual parts.
Use digikey_search_parts to discover candidates, then call digikey_get_part_details and digikey_validate_bom before saying a part is ready to buy.
In final order lists, use the exact DKPN and distinguish the DigiKey part number (DKPN) from the manufacturer part number (MPN). Never invent either identifier, a price, stock value, URL, datasheet, or compatibility claim.
Keep requested quantity separate from purchase quantity. Account for MOQ, package increments, cut tape/reel constraints, and spares; surface the arithmetic.
Label every line as VERIFIED_MATCH, VERIFIED_WITH_ASSUMPTION, POSSIBLE_MATCH, or NO_VERIFIED_PART_FOUND. Only the first two belong in the default order export.
Keep custom, user-provided, non-DigiKey, and unresolved items in their own section.
Surface mating/interface consistency, open decisions, datasheet/layout/thermal review, and professional safety review when the evidence cannot support a stronger conclusion.
When asked “which one is better?”, use digikey_compare_candidates and explain user-dependent trade-offs instead of declaring an objective winner.

Read the detailed workflow and status rules here:

Scenario references:

Read the full file on GitHub · 59 lines

Files

What ships with it

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

2mo ago First seen · 59 lines · 17 tokens per session scan A 88f13b4f229b

Subscribe to this mod's changes

digikey-bom is a skill published in the GitHub repository itsyashk/digikey-mcp (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 700 once invoked, about $0.0001 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-08-31.

Hardware and IoT

digikey-bom next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
digikey-bomitsyashk/digikey-mcp	Skill	0	3mo ago	Apache-2.0	A	17	Claude Code, Codex
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
jetson-diagnosticNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code, Codex
holoscan-install-wheelNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	34	Claude Code, Codex
offensive-z-waveSnailSploit/Claude-Red	Skill	10k	25d ago	MIT	A	113	Claude Code, Codex
doca-socket-relayNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	236	Claude Code, Codex
hsb-flashNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	B	94	Claude Code