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/.agents/skills/pio-manager/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/pio-manager)<a href="https://agentmods.dev/skills/jl-codes/platformio-mcp/pio-manager"><img src="https://agentmods.dev/badge/skills/jl-codes/platformio-mcp/pio-manager.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.1 | $0.00120 | $0.01989 |
| Opus 5 | $0.00060 | $0.00994 |
| Sonnet 5 | $0.00024 | $0.00398 |
| Haiku 4.5 | $0.00012 | $0.00199 |
Grade A, and why
pio-manager 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 7d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PIO Manager (Mega-Skill)
This skill provides the mandatory 3-Tier Execution Architecture for interacting with PlatformIO builds, hardware flashing, and serial port logs. All agents MUST consult this skill before executing any target compilation.
The 3-Tier Execution Hierarchy
🟢 Tier 1 (Preferred): MCP Server Primitives
The platformio-mcp server encapsulates atomic locking, compilation, and log spooling safely. You must ALWAYS attempt to use these tools first:
- Compilation/Deployment/Analysis:
mcp_platformio_build_project,mcp_platformio_clean_project,mcp_platformio_upload_firmware,mcp_platformio_upload_filesystem,mcp_platformio_check_project,mcp_platformio_run_tests - Asynchronous Polling:
mcp_platformio_check_task_status - Hardware Locking:
mcp_platformio_get_lock_status,mcp_platformio_acquire_lock,mcp_platformio_release_lock,mcp_platformio_reset_server_state - Serial Monitor:
mcp_platformio_start_monitor,mcp_platformio_stop_monitor,mcp_platformio_query_logs - Environment/Libraries:
mcp_platformio_list_boards,mcp_platformio_get_board_info,mcp_platformio_list_devices,mcp_platformio_init_project,mcp_platformio_search_libraries,mcp_platformio_install_library,mcp_platformio_uninstall_library,mcp_platformio_update_library,mcp_platformio_list_installed_libraries - Diagnostics/Dashboard:
mcp_platformio_get_dashboard_url,mcp_platformio_get_project_config,mcp_platformio_system_info
Reference: For exact tool parameters and best practices, load and read references/mcp-agent-reference.md.
Discovery Best Practices:
- ALWAYS use
mcp_platformio_list_boardsto dynamically find a board before trying to query specs withmcp_platformio_get_board_info. - ALWAYS use
mcp_platformio_list_devicesbefore uploading or monitoring to discover the correctportdynamically if multiple serial devices are attached. - ALWAYS use explicit versions when using
mcp_platformio_install_libraryto ensure reproducible builds.
What ships with it
10 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.
- assets/build.sh 123 B runs code
- assets/clean.sh 141 B runs code
- assets/flash.sh 143 B runs code
- assets/read-logs.py 2.0 KB runs code
- assets/safe-flash.sh 1.9 KB runs code
- references/esp32-macos-tuning.md 3.6 KB
- references/mcp-agent-reference.md 6.1 KB
- references/v6-hardware-less-emulation.md 1.7 KB
- references/v6-pkg-exec-sandboxing.md 2.7 KB
- scripts/install_pio_mcp_server.py 3.1 KB runs code
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.
- 7d ago First seen · 80 lines · 120 tokens per session scan A 7afb70d4be31
pio-manager is a skill published in the GitHub repository jl-codes/platformio-mcp (50 stars, last pushed today), licensed MIT. It adds 120 tokens to every session and 1,989 once invoked, about $0.0006 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
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
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.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
ros2-robotics
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…
code-plan
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.