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 step1-onboardgit 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/step1-onboard)<a href="https://agentmods.dev/skills/raisoninme/boardless-pcb/step1-onboard"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/step1-onboard/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/step1-onboard"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/step1-onboard.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.00024 | $0.02149 |
| Opus 5 | $0.00012 | $0.01074 |
| Sonnet 5 | $0.00005 | $0.00430 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
step1-onboard 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 10d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 1 · Onboarding
Session check (do this first)
One step per session. If this session has already done other substantive work, stop and ask the user to start a fresh session.
Then look for docs/flow-state.md (recognize it by its canonical header line flow-state — process state; a foreign file under this name → stop and ask the user to rename or confirm):
- Missing → fresh start: create it now from the template in §4, with step 1 =
in-progress— an aborted onboarding must stay visible and resumable. - Present, step 1
in-progress→ a previous onboarding aborted (often a toolchain-install restart): resume, don't restart. Check which artifacts already exist (docs/requirements.mdconfirmed?docs/dev-plan.mdconfirmed? toolchain installed?) and continue from the first missing one. Never re-interview for answers already on disk. - Present, step 1
done→ re-run: ask what the user intends (amend requirements? restart?) before overwriting anything.
Interact and generate all project documents in the user's language. Canonical English is kept only for machine-parsed values: status tokens (steps not-started / in-progress / done / rework / waiting / parked; issues open / fixed-pending-verify / closed / deferred; severity nondeferrable / major / minor), issues-table target-step values (2 3 4 5 step6), and the flow-state header line.
Execute
1. Context interview
Interview the user; ask at most 3–4 questions at a time (multiple choice with a recommended option):
- First, one routing question: greenfield (from scratch) or brownfield (iterating on an existing version)?
- Greenfield track: product definition / must-have feature list ("must", not "nice-to-have") / top-priority metric(s) — push each to a quantified, selection-vetoing criterion (one is typical, more is fine; not every metric decomposes per part) / explicit non-goals
- Brownfield track: directory & version map / what to ignore (material not ruled out gets read and confabulated from) / scope of this iteration / reference pointer in three parts (which version + which part + for what understanding) / trust level of existing assets (verified-rely-on vs reference-only-reverify; selection rules apply to new and changed parts, inherited verified parts keep their trust level) / EDA migration statement (an old project in another EDA is reference material, never the base document)
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.
- 10d ago First seen · 111 lines · 24 tokens per session scan A 7dd20b32079e
step1-onboard is a skill published in the GitHub repository raisoninme/boardless-pcb (2 stars, last pushed 27d ago), licensed MIT. It adds 24 tokens to every session and 2,149 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
review
Review branch changes against Archcore docs, or report project health. Use for 'review my branch', 'review the changes before merge', 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. --drift for staleness…
plan
Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Expert paths: sdd (full package), sources mode (MRD → BRD → URD) for…
template-eda-notebook
Exploratory data analysis notebook exemplar — notebook-to-src extraction workflow, tested EDA library, deterministic dataset, diagnostic figures.
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.
fec-component-testing
A guide for writing and reviewing front-end unit, component, and lightweight integration tests. These tests check small pieces of code and UI behavior without running a full browser journey.