Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mawildoer/atopile-agent-skillnpx agentmods add skills/mawildoer/atopile-agent-skill/build-and-testWrote 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/mawildoer/atopile-agent-skill/build-and-test)<a href="https://agentmods.dev/skills/mawildoer/atopile-agent-skill/build-and-test"><img src="https://agentmods.dev/badge/skills/mawildoer/atopile-agent-skill/build-and-test/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/mawildoer/atopile-agent-skill/build-and-test"><img src="https://agentmods.dev/badge/skills/mawildoer/atopile-agent-skill/build-and-test.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.00049 | $0.01833 |
| Opus 5 | $0.00024 | $0.00916 |
| Sonnet 5 | $0.00010 | $0.00367 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade B, and why
build-and-test 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 11d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Run any command with `--help` for full flag details. How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build & Test Workflow
Typical Order
ato validate <file.ato>-- quick syntax check. Catches parse errors before a full build. No solver, no parts, no PCB. Use after editing .ato files to confirm they parse cleanly.ato build-- the main command. Runs from the project directory (whereverato.yamllives). Stages in order: resolve dependencies, build context, instantiate, verify design, pick parts from JLCPCB, update PCB, generate reports. A successful build means the design is electrically valid and all parts are available.ato build --open-- same as above, then launches KiCad layout editor so you can inspect/route the PCB.ato build -b <name>-- build a specific target fromato.yaml(e.g.ato build -b test). Useful when a project has multiple build targets.ato build --verbose-- runs sequentially without the live display. Better for reading error messages.ato inspect-- debug connectivity. Shows what is connected to a module at a given boundary. Use--inspect <module> --context <parent>to see connections from a specific viewpoint.ato create part -s "<search>"-- search JLCPCB and generate a component package (.ato + KiCad footprint/symbol) inparts/. Interactive: presents matches and lets you pick.
Run any command with --help for full flag details.
Build Outputs
After a successful build, outputs land in build/builds/<target>/:
| File | Contents |
|---|---|
<target>.bom.csv |
Bill of materials -- designators, footprints, manufacturer, LCSC part numbers |
<target>.bom.json |
Same BOM in JSON format |
<target>.variables.ato.json |
All solved parameter values -- spec vs actual, whether constraints are met |
<target>.power_tree.ato.json |
Power tree structure (JSON) |
power_tree.md |
Power tree as Mermaid diagram |
<target>.data_interface_tree.ato.json |
Data interface topology |
pinout/ |
Per-component pinout JSON files |
backups/ |
PCB backup snapshots |
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.
- 11d ago First seen · 135 lines · 49 tokens per session scan B 97bfa303d324
build-and-test is a skill published in the GitHub repository mawildoer/atopile-agent-skill (10 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,833 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…