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 Ed3Design/ed3design-engineering-bundles --skill bom-validation-workflowgit clone --depth 1 https://github.com/Ed3Design/ed3design-engineering-bundlesWrote 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/ed3design/ed3design-engineering-bundles/bom-validation-workflow)<a href="https://agentmods.dev/skills/ed3design/ed3design-engineering-bundles/bom-validation-workflow"><img src="https://agentmods.dev/badge/skills/ed3design/ed3design-engineering-bundles/bom-validation-workflow.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.00181 | $0.01832 |
| Opus 5 | $0.00090 | $0.00916 |
| Sonnet 5 | $0.00036 | $0.00366 |
| Haiku 4.5 | $0.00018 | $0.00183 |
Grade A, and why
bom-validation-workflow 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 7d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BOM Validation Workflow
When a Maker-3D project (embedded controller, audio build, smart-home build) has its component list defined, the typical next step is: create an order list. A frequent failure point: connection parts (cables, connectors, screws), consumables (filament, solder, thermal paste), and existing stock are forgotten. Result: 2-3 deliveries instead of one, plus blocked wait time.
This skill brings a disciplined workflow: extract the BOM, reconcile with the hardware stock, identify missing components CATEGORIZED (main parts, connections, consumables), deliver an order list with estimated prices + sources.
When to use
- A spec note has a component table or list (>5 items)
- Before an order at a parts retailer / Amazon / AliExpress
- During the transition from design phase to build phase (see
design-first-iteration+cad-construction) - When the user asks "can I build this now?" or "what's still missing?"
- Cross-project check: ordering a part useful for multiple projects together
When NOT to use
- Pure software projects with
requirements.txt/package.json— other tools - Schematic reviews without a physical component question (schematic check is separate)
- Projects with 1-2 components — discipline overhead not justified
- The spec note doesn't have a BOM table yet — first finish design, then extract BOM
Workflow (4 phases)
Phase 1: BOM extraction from spec
Read the project spec note and extract ALL components. Pay particular attention to:
- Main parts: microcontrollers, sensors, actuators, displays, batteries
- Structural parts: printed parts (with material + quantity), aluminium profiles, wood
- Connection parts (often forgotten): cables with lengths, connectors (JST/Dupont/XT60), screws (size + length + material), nuts, standoffs
- Consumables: filament quantities (in grams), solder, flux, thermal paste, cable ties, heat-shrink tubing
- Hidden prerequisites: power supply (adapter + plug), tools you don't yet own, programming adapters
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.
- 7d ago First seen · 137 lines · 181 tokens per session scan A 66c585123a25
bom-validation-workflow is a skill published in the GitHub repository Ed3Design/ed3design-engineering-bundles (2 stars, last pushed 1mo ago), licensed MIT. It adds 181 tokens to every session and 1,832 once invoked, about $0.0009 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-31.
Other skills, from other repositories
ros2-microros
Skill "ros2-microros" from Leehyunbin0131/claude-ros2-skills, covering micro-ros instructions (ubuntu 24.04 lts & ros 2 jazzy), 1. architecture, 2. documentation entry points, 3. key concepts & patterns and a. embedded client node setup (rclc in c).
nurb
Design 3D-printable parts as Python functions with nurb. Use when the user wants a part designed, changed, or checked for 3D printing (a bracket, mount, holder, enclosure, shelf, or any STL/STEP to print), and in any directory with a parts/ folder. The user describes the part and judges it in a browser; you model it.
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
esp32-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO)…
continuum-fea
Run the continuum (tier-3) FEA on a part a beam model can't capture — bracket, fitting, lug, hull bottom panel, pressure shell, sponson root — with gmsh + CalculiX (ccx). Use when an audit's analytic check or the in-house beam FEA is too coarse and you need a real 3-D stress/displacement or buckling field. Drives the…
add-scored-audit
Add a new executable scored check (PASS/WARN/FAIL) for a requirement to a hardware-as-code project's audit harness. Use when a requirement, clearance, mass budget, margin, or anchor needs to be verified automatically. Enforces the rules: read the build's exported JSON artifacts, never duplicate a geometry constant…