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 flow-guidegit 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/flow-guide)<a href="https://agentmods.dev/skills/raisoninme/boardless-pcb/flow-guide"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/flow-guide/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.
<a href="https://agentmods.dev/skills/raisoninme/boardless-pcb/flow-guide"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/flow-guide.svg" alt="Reviewed on agentmods" width="80" 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.00124 | $0.01576 |
| Opus 5.5 | $0.00050 | $0.00630 |
| Sonnet 5.5 | $0.00025 | $0.00315 |
| Haiku 4.5 | $0.00012 | $0.00158 |
Grade A, and why
flow-guide 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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Guide (explains, never executes)
This skill answers "what is this workflow and why is it designed this way".
Execution is driven exclusively by the user invoking the step skills, one step per session. You (the model) must not advance any step without its skill being invoked, must not decide to enter the next step on the user's behalf, and must not skip ahead just because the user says "continue". User wants to start → point them to step1-onboard (Claude Code: /boardless-pcb:step1-onboard); user lost track → status (Claude Code: /boardless-pcb:status).
Language: always interact in the user's language, and generate project documents in the user's language. Only the flow-state status tokens stay as canonical English strings (see below) so any later session can parse them reliably.
The seven steps
1 onboarding (context interview → dev plan → toolchain → state init)
2 firmware skeleton, freeze the pin map ← firmware exists here to produce pin constraints
3 schematic design (incl. component selection)
4 placement ← hard gate: board outline/structure is the user's call
5 routing
6 per-module simulation verification ← amnesia subagent; autonomous local-fix loop
7 full firmware integration ← closing hard gate: human visual inspection
One skill per step: step1-onboard … step7-integrate, plus status to locate yourself from any new session. On Claude Code they are invoked as /boardless-pcb:<name>; on Codex as $<name>; on Cursor as /<name>.
Why one step per session
- Self-sufficient deliverables are the goal; fresh sessions are the means. Every command rebuilds context exclusively from files on disk (
docs/flow-state.md+ the previous step's deliverables), never from conversation memory. If the next step cannot start from disk alone, the previous step's deliverables were incomplete — exposed immediately. - Session boundaries follow "entering a step", not step numbers. Step 6 is the structural exception: once entered, the verify → autonomous-fix → re-verify loop stays in one session. Context purity is carried by the amnesia subagent's mechanical isolation (every re-verification is a brand-new instance), not by session boundaries. Only structural rework (board outline / assembly mode / layer count — requires user approval) moves to the corresponding step command in a new session.
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.
- 1mo ago First seen · 60 lines · 124 tokens per session scan A c97149978d7d
flow-guide is a skill published in the GitHub repository raisoninme/boardless-pcb (2 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 1,576 once invoked, about $0.0005 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.
Other skills, from other repositories
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
learn
Explain recent vibe-learn session activity or answer a question about what was built, grounded in .vibe-learn/session-log.jsonl.
quiz
Check your understanding of the vibe-learn session — recall questions grounded in the session log, with results tracked across sessions in the knowledge ledger.
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. Handles project setup…
vibe-learn
Explain, digest, quiz, and tour the code of the current vibe-learn coding session, with cross-session knowledge tracking and optional Obsidian save and recall workflows grounded in .vibe-learn/session-log.jsonl.