Borrowing it
Nothing to install: this file belongs to jl-codes/platformio-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jl-codes/platformio-mcp/main/.skills/firmware-bringup/SKILL.mdgit clone --depth 1 https://github.com/jl-codes/platformio-mcpWrote 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/jl-codes/platformio-mcp/firmware-bringup)<a href="https://agentmods.dev/skills/jl-codes/platformio-mcp/firmware-bringup"><img src="https://agentmods.dev/badge/skills/jl-codes/platformio-mcp/firmware-bringup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00303 |
| Opus 5 | $0.00029 | $0.00151 |
| Sonnet 5 | $0.00012 | $0.00061 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
firmware-bringup 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 8d 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.
What it actually says
Firmware Bringup
Purpose
Use this skill when the user wants to bring up a new embedded board or create a minimal working firmware project.
Safety Rules
- Do not flash firmware without explicit user approval.
- Do not erase flash unless the user explicitly asks.
- Do not assume the serial port. Discover connected devices first.
- Preserve logs and task IDs for debugging.
Workflow
- List connected devices.
- Search for the likely PlatformIO board ID.
- Initialize or inspect the project.
- Add a minimal boot marker, such as
BOOT_OK, to serial output. - Build the project.
- If build succeeds, ask the user before flashing.
- Flash the firmware after approval.
- Start serial monitoring.
- Verify expected boot output.
- Summarize result and next steps.
Preferred Commands
Use available repo tools or CLI commands equivalent to:
pio-mcp devices
pio-mcp boards search esp32
pio-mcp init --board esp32dev --framework arduino
pio-mcp build
pio-mcp flash --port auto
pio-mcp monitor --timeout 30
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.
- 8d ago First seen · 44 lines · 58 tokens per session scan A b09339512280
firmware-bringup is a skill published in the GitHub repository jl-codes/platformio-mcp (50 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 303 once invoked, about $0.0003 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-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.