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 agentmods add skills/raisoninme/boardless-pcb/setupnpx skills add raisoninme/boardless-pcb --skill setupgit 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/setup)<a href="https://agentmods.dev/skills/raisoninme/boardless-pcb/setup"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/setup.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 | $0.00059 | $0.00913 |
| Opus 5 | $0.00030 | $0.00456 |
| Sonnet 5 | $0.00012 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade B, and why
setup scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Codex loads project-level `.codex/agents/` **only in trusted projects**. You cannot grant that for the user. Tell them: trust the project when Codex asks on first open, or add it under `[projects]` in `~/.codex/config.to How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup — finish the install (Codex / Cursor)
npx skills installs skills and nothing else. Two parts of boardless-pcb are not skills:
- the amnesia-verifier subagent that Step 6 delegates its independent audit to
- the always-on workflow rules that belong in the project's
AGENTS.md
This skill installs both from the files bundled beside it, into the project the user is working in. Run it once per project. It is idempotent: re-running reports what is already in place instead of duplicating it.
Respond in the user's language.
1. Host platform
- Claude Code → nothing to do. The plugin already ships the subagent and the anti-patching hook. Say so, point the user at
/boardless-pcb:step1-onboard, and stop here. - Codex → §2, using
assets/codex/amnesia-verifier.toml→<project>/.codex/agents/amnesia-verifier.toml - Cursor → §2, using
assets/cursor/amnesia-verifier.md→<project>/.cursor/agents/amnesia-verifier.md - Anything else → say plainly that this workflow has only been built for these three, and stop. Do not improvise a target directory.
Confirm the project root with the user before writing anything — this must land in the PCB project, not in whatever directory the session happens to start in.
2. Install the subagent
Copy the file for the detected platform, byte for byte. Do not summarize, reformat, or "improve" it: its wording is the whole mechanism — an independent reviewer that reads only live EDA data is what makes Step 6 catch what the main agent cannot.
- Target missing → create the directory and copy.
- Target already identical → report "already installed", change nothing.
- Target exists and differs → show the user what differs and ask before overwriting. A user may have hardened it deliberately (for example by narrowing its tool access); do not silently undo that.
3. Install the always-on rules
Append assets/AGENTS-snippet.md to <project>/AGENTS.md, creating the file if it does not exist. If a # boardless-pcb workflow rules heading is already present, leave it alone and report it — never append a second copy.
What ships with it
4 files 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.
- 3d ago First seen · 55 lines · 59 tokens per session scan B 53369e0bbdd1
setup is a skill published in the GitHub repository raisoninme/boardless-pcb (2 stars, last pushed 21d ago), licensed MIT. It adds 59 tokens to every session and 913 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dev
Implement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for "implement", "build/code this plan", or targeted fix findings. If no plan exists, use /ship:design first.
handoff
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
e2e
Add durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA.
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…
refactor
Improve existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.
write-docs
Create or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself…