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/hardware-in-the-loop-test/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/hardware-in-the-loop-test)<a href="https://agentmods.dev/skills/jl-codes/platformio-mcp/hardware-in-the-loop-test"><img src="https://agentmods.dev/badge/skills/jl-codes/platformio-mcp/hardware-in-the-loop-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/jl-codes/platformio-mcp/hardware-in-the-loop-test"><img src="https://agentmods.dev/badge/skills/jl-codes/platformio-mcp/hardware-in-the-loop-test.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00240 |
| Opus 5 | $0.00020 | $0.00120 |
| Sonnet 5 | $0.00008 | $0.00048 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
hardware-in-the-loop-test 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 9d 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
Hardware-in-the-Loop Test
Purpose
Use this skill to validate firmware behavior on a real device, not just through compilation.
Safety Rules
- Ask before flashing.
- Do not assume physical wiring is safe.
- Do not activate motors, heaters, lasers, relays, pumps, or high-power outputs without explicit user approval.
- Keep tests bounded by timeout.
- Save logs and artifacts.
Workflow
- Define expected behavior.
- Build firmware.
- Ask before flashing.
- Flash firmware.
- Monitor device output.
- Check expected serial strings, timing, or telemetry.
- Mark pass/fail.
- Save build logs, flash logs, and serial logs.
- Summarize results.
Example Test Definition
name: esp32_boot_marker
board: esp32dev
expected:
serial_contains: BOOT_OK
timeout_seconds: 15
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.
- 9d ago First seen · 41 lines · 41 tokens per session scan A 44cd219605a5
hardware-in-the-loop-test is a skill published in the GitHub repository jl-codes/platformio-mcp (50 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 240 once invoked, about $0.0002 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.