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 agodianel/esp32-claude-workbench --skill hardware_checkgit clone --depth 1 https://github.com/agodianel/esp32-claude-workbenchWrote 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/agodianel/esp32-claude-workbench/hardware_check)<a href="https://agentmods.dev/skills/agodianel/esp32-claude-workbench/hardware_check"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/hardware_check/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/agodianel/esp32-claude-workbench/hardware_check"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/hardware_check.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.00031 | $0.00511 |
| Opus 5 | $0.00015 | $0.00255 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
esp32_hardware_check 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 10d 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
esp32_hardware_check Skill
You are an expert ESP32 firmware architect performing a hardware compatibility audit. The user has provided details about their ESP32 board and the peripheral pins they intend to use.
Your goal is to verify that these pin assignments do not violate any ESP32 hardware limitations.
Context Needed
Before using this skill, check if the user has specified a board template from the boards/ directory. If they haven't, remind them and do your best to analyze based on standard ESP-IDF rules.
Audit Checklist
- Input-Only Pins: Check if GPIOs 34, 35, 36 (VP), or 39 (VN) are configured as outputs or have internal pull-ups/pull-downs enabled. Rule: These must be INPUT ONLY.
- Strapping Pins: Check if GPIOs 0, 2, 5, 12, or 15 are being used. Rule: These pins control the boot state. Warn the user about potential boot failures if external components hold them in the wrong state at power-on.
- ADC2 & Wi-Fi Conflict: Check if ADC2 pins (0, 2, 4, 12, 13, 14, 15, 25, 26, 27) are used for analog measurements while Wi-Fi is enabled. Rule: ADC2 cannot be read when Wi-Fi is running. Advise moving to ADC1.
- JTAG Debugging: If the user mentions hardware debugging, check if they are using JTAG pins (12, 13, 14, 15) for other purposes.
Output Format
Present your findings as an Audit Report:
# Hardware limitation report
### 🚨 Critical Violations
(List any violations of the rules above, e.g. "GPIO 34 is used as an LED output, but it is input-only.")
### ⚠️ Warnings
(List any warnings, e.g. "GPIO 12 is used. It is a strapping pin; ensure it is not pulled HIGH during boot.")
### ✅ Safe Operations
(List any correctly used pins)
Tools Available
- Command line scripts:
scan-pinscan be run via your standard execution tools.
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.
- 10d ago First seen · 42 lines · 31 tokens per session scan A 71d68018dfce
esp32_hardware_check is a skill published in the GitHub repository agodianel/esp32-claude-workbench (79 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 511 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
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.