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 step4-placementgit 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/step4-placement)<a href="https://agentmods.dev/skills/raisoninme/boardless-pcb/step4-placement"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/step4-placement/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/step4-placement"><img src="https://agentmods.dev/badge/skills/raisoninme/boardless-pcb/step4-placement.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.00028 | $0.00968 |
| Opus 5.5 | $0.00011 | $0.00387 |
| Sonnet 5.5 | $0.00006 | $0.00194 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
step4-placement 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 4 · Placement
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 3 isdone; read the schematic/netlist deliverables, BOM,docs/pinmap.md. Not satisfied → stop and report. - This step already
donewith no issue targeting it → re-run: ask intent first. Alreadyin-progress→ aborted or concurrent session: ask before proceeding. Markedrework→ redo what the rework note requires, then wrap up. - Issues-table entries with target step = 4 → fix mode.
- Set step 4
in-progress. Rebuild context from disk only.
Execute
Adopt-and-audit path: an inherited placement recorded in flow-state (inherited: <path>, same-EDA only) is ingested, then audited by this step's own checks — the structure gate below still runs (the enclosure decision is the user's even when the placement is theirs), and the four self-checks must pass at zero. The bar doesn't move; only the labor does.
⛔ Hard gate (before any placement work; the AI must not wave itself through)
Board outline, component side, and orientation are enclosure-level decisions — the user's, not your defaults.
- Pull real mechanical data from the key components' official specs (outlines, clearances, connector exit positions)
- Distill the concrete structural conflicts (e.g. what doesn't fit in which clearance, who competes for which board edge, what large mechanical parts — battery, display, shield, heatsink — cover)
- Cross-check the structure decisions against
docs/fab-profile.md— layer count, stackup, and clearances must be achievable in the frozen profile; changing the profile is a plan amendment, never a silent swap - Have the user decide via multiple-choice with a recommended option; only then generate coordinates
The structure gate is re-entrant: if packing later proves the confirmed decisions infeasible — or shows the layer count itself must change — come back to the user with the evidence and re-decide before continuing (and amend the dev-plan if the stackup/power-plane strategy changes). Never force a fit past a decision the evidence has invalidated.
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.
- 1mo ago First seen · 43 lines · 28 tokens per session scan A 1d53f7410184
step4-placement is a skill published in the GitHub repository raisoninme/boardless-pcb (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 968 once invoked, about $0.0001 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
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…
metago-thought-14-ambient-intelligence
A framework for assessing intelligence built into physical environments, such as smart spaces and embedded systems. It focuses on whether sensing and computing blend naturally into the surroundings and adapt to users.
metago-thought-16-spatial-agent
A framework for designing and evaluating interfaces that use physical space as part of the interaction, such as sensors, projection, augmented reality, voice, or gestures. It treats the environment itself as an interface rather than limiting interaction to a screen.
nightmarquee-wren
Wren: The companion app for a robot that lives with you. A home-robot app that feels like hardware: a live camera card that tags what the robot sees, a voice orb that turns a sentence into a queued task, a CSS-3D floor plan you spin with a finger while the robot re-plans around a toy, and teach-by-demonstration with a…
cad-construction
Use after the design concept is settled (via design-first-iteration or equivalent) and the user is ready to translate it into parametric CAD geometry — component decomposition, parameter hierarchy, construction sequencing. Primary platform Fusion 360; the workflow also applies to SolidWorks, Onshape, FreeCAD…
figma-design-system-to-design-md
Figma design system to design.md — Extract Figma design system into a structured design.md. Use when user says 'generate design.md', 'extract design system', 'design tokens to markdown', 'create design doc from Figma', 'Figma design system to design.md', or wants to document their design system from token files and…