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 raisoninme/boardless-pcb --skill step7-integrategit clone --depth 1 https://github.com/raisoninme/boardless-pcbWrote 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/raisoninme/boardless-pcb/step7-integrate)<a href="https://agentmods.dev/skills/raisoninme/boardless-pcb/step7-integrate"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/step7-integrate.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.00024 | $0.01486 |
| Opus 5 | $0.00012 | $0.00743 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
step7-integrate 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 7 · Full firmware integration & closing
Session & state check (before touching anything)
- One step per session: if this session already did substantive work for another step, stop and ask for a fresh session.
- Read
docs/flow-state.md(canonical header line; foreign file → stop and ask). Confirm step 6 isdoneand the open-issues table has noopenorfixed-pending-verifyentries (deferredentries pass this gate — they are settled at the definition-of-done below). Readdocs/dev-plan.md,docs/pinmap.md, the module inventory and verification summary. Not satisfied → stop and report. - This step already
done→ re-run: ask the user's intent first. Alreadyin-progress→ a previous session aborted (normal for long integration work) or another session is live: ask, then resume from the on-disk state. Alreadywaiting(release findings routed to their steps, or an integration handoff sent to step 6) → this re-entry is expected once they clear: resume where you left off — integration (§1–2) after a settled handoff, the §4 readback after release findings. - Set step 7
in-progress. Rebuild context from disk only.
Execute
1. Full firmware
Flesh out the interfaces frozen in step 2 into complete business logic, feature by feature against the plan's feature list (e.g. control logic, UI, storage, communication, power management — whatever the product defines). For paths the platform-capability probe marked "not simulatable", use multi-source evidence (full host state-machine coverage + mocked API argument assertions + official documentation citations) and phrase the DoD conditionally.
2. Firmware-first debugging (the priority inverts here)
By this step the hardware has been verified module by module, so when a bug appears the default attribution is firmware. Solve it on the firmware side first — logic, driver usage, init order, timing/peripheral configuration — exhausting candidate fixes autonomously: try one, check it against the failing behavior, roll back and log the ones that didn't hold, and consult the user for none of it. Never touch the PCB in this loop:
What ships with it
1 file 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.
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 · 67 lines · 24 tokens per session scan A 521de9fa21f1
step7-integrate is a skill published in the GitHub repository raisoninme/boardless-pcb (2 stars, last pushed 25d ago), licensed MIT. It adds 24 tokens to every session and 1,486 once invoked, about $0.0001 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
kicad-jlcpcb-workflow
Use this skill when the user asks to "design a PCB", "make a board", "build a PCB project", "order from JLCPCB", "create a schematic", "source LCSC parts", "wire up a board", "generate a PCB from a BOM", or any KiCad + JLCPCB workflow. Also use when working with .kicadpro or .kicadpcb files. Phase 1.6 handles project…
spark-environment-setup
Set up a working ML training/inference environment on NVIDIA DGX Spark (GB10, aarch64, CUDA 13). Use when installing PyTorch/Unsloth/TRL/vLLM on DGX Spark, hitting libcudart or wheel-ABI errors on aarch64, or choosing between NGC containers and bare pip installs.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
kicad
Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label…
lcsc
Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (--mpn-list)…
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…