pcb-from-bom

pcb-from-bom is a command for Claude Code from BeckhamLabsLLC/kicad-jlcpcb. It costs 30 tokens per session (781 once invoked), scanned A, original, MIT.

A command for starting a KiCad printed-circuit-board project from a CSV bill of materials, a parts list containing LCSC part numbers.

In plain words
What is it for?
Use it to resolve an LCSC BOM, create or resume a KiCad project, map component pins, and prepare a wired board file.
Why use it?
It skips initial part sourcing and checks whether listed parts are valid, available, and priced before wiring the board.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the kicad-jlcpcb plugin — 1 skill, 2 commands, 1 agent, 1 MCP server shipped together

Good fit Use it to resolve an LCSC BOM, create or resume a KiCad project, map component pins, and prepare a wired board file.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-bom
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.

Clone the repo
git clone --depth 1 https://github.com/BeckhamLabsLLC/kicad-jlcpcb

Made for: Claude Code.

Or install kicad-jlcpcb, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent, 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 pcb-from-bom

README.md
[![agentmods](https://agentmods.dev/badge/commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-bom/github.svg)](https://agentmods.dev/commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-bom)
Your own site
<a href="https://agentmods.dev/commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-bom"><img src="https://agentmods.dev/badge/commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-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.

agentmods 80×15 button for pcb-from-bom

Your own site · 80×15
<a href="https://agentmods.dev/commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-bom"><img src="https://agentmods.dev/badge/commands/beckhamlabsllc/kicad-jlcpcb/pcb-from-bom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 781 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00781
Opus 5 $0.00015 $0.00391
Sonnet 5 $0.00006 $0.00156
Haiku 4.5 $0.00003 $0.00078

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

Security

Grade A, and why

pcb-from-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 12d 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.

commands/pcb-from-bom.md · 64 lines

How it starts

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

/pcb-from-bom

Start a KiCad project from an existing BOM CSV. Skips part sourcing and goes straight to pin-map fetch + wired .kicad_pcb + EasyEDA handoff.

Instructions

1. Detect KiCad, create or resume the project

Call detect_kicad. If the target project directory already exists, call load_project on it and check the returned session summary — if resume_available is true, offer the user a resume-or-restart choice (same pattern as /pcb-new step 2). Otherwise call create_project.

2. Read the BOM

Use Read to load the CSV. Auto-detect the column layout — common forms:

  • Reference, Value, LCSC, Quantity
  • Designator, Value, LCSC Part #, Qty
  • Comment, Designator, Footprint, LCSC

Convert each row into a {lcsc, qty} dict.

3. Resolve the BOM

Call lcsc_resolve_bom with the rows. Validates every C-number against the live jlcparts mirror and catches any out-of-stock or discontinued parts.

4. CHECKPOINT — present the BOM

Same as /pcb-new step 5. Show the user resolved/unresolved/cost and get confirmation.

5. Interpret design intent

If the BOM file has a design-intent section (GPIO table, functional descriptions, schematic notes) or the user provided notes alongside the BOM:

a. Read it carefully. The design intent tells you how parts connect.

b. Map every IC to a reasonable footprint. KiCad stdlib names are listed in /pcb-new step 6. For ICs not in KiCad stdlib, pick the closest package-family footprint (SOT-23-6, QFN-24, SOIC-8, etc.) — the user can swap it in EasyEDA later.

c. Call part_pin_map for each IC whose pinout you're unsure about. It returns {pin_name: pad_num} so you know what the nets need to reference.

d. Build the nets dict. Map power rails, buses (I2C, SPI, UART, USB), and signal lines based on the design intent. Reference pins by name, not number — the plugin resolves them.

If the BOM has no design intent and the user provided no notes: warn them that you'll generate a components-only spec (no nets), and they'll have to wire things up manually in KiCad or EasyEDA.

Read the full file on GitHub · 64 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. 12d ago First seen · 64 lines · 30 tokens per session scan A f8e860b95322

Subscribe to this mod's changes

pcb-from-bom is a command published in the GitHub repository BeckhamLabsLLC/kicad-jlcpcb (24 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 781 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.