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 esp32_pin_auditgit 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/esp32_pin_audit)<a href="https://agentmods.dev/skills/agodianel/esp32-claude-workbench/esp32_pin_audit"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/esp32_pin_audit/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/esp32_pin_audit"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/esp32_pin_audit.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.00022 | $0.00752 |
| Opus 5 | $0.00011 | $0.00376 |
| Sonnet 5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
esp32_pin_audit 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 12d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ESP32 Pin Audit
Systematically audit GPIO pin usage across the project to detect conflicts, reserved pin misuse, and undocumented assignments.
When to Use
- Before adding new peripheral code.
- During architecture review.
- When debugging mysterious hardware behavior.
- Before release.
Steps
1. Collect All Pin Declarations
Search the project for pin definitions:
# Macro definitions
grep -rn "#define.*GPIO\|#define.*PIN\|#define.*SDA\|#define.*SCL\|#define.*MOSI\|#define.*MISO\|#define.*CS\|#define.*CLK" --include="*.h" --include="*.c"
# GPIO_NUM usage
grep -rn "GPIO_NUM_" --include="*.c" --include="*.h"
# Kconfig GPIO options
grep -rn "CONFIG_.*GPIO\|CONFIG_.*PIN" sdkconfig.defaults sdkconfig 2>/dev/null
2. Check Reserved Pins
Flag violations against these reserved pins:
| GPIO | Restriction | Reason |
|---|---|---|
| 0 | Boot strapping | Must be HIGH for normal boot, LOW for download |
| 1 | UART0 TX | Default serial output |
| 2 | Boot strapping | Must be LOW during flash |
| 3 | UART0 RX | Default serial input |
| 6–11 | FORBIDDEN | Connected to internal SPI flash |
| 12 | Boot strapping | MTDI — affects flash voltage |
| 15 | Boot strapping | MTDO — affects debug output |
| 34–39 | Input-only | No output capability, no pull-up/pull-down |
3. Detect Conflicts
Build a pin allocation table and check for:
- Double assignment: Same GPIO used by two different peripherals.
- Bus conflicts: I2C and SPI sharing the same pins.
- ADC/DAC conflicts: ADC2 channels unusable when Wi-Fi is active.
- Strapping conflicts: Boot pins used without awareness.
4. Verify Pull-Up/Pull-Down Configuration
For I2C lines:
- External pull-ups are required. Internal pull-ups are too weak for reliable I2C.
- Flag if only internal pull-ups are configured for I2C.
For inputs with no external circuitry:
- Verify pull-up or pull-down is configured to avoid floating pins.
5. Check Documentation
Compare actual code pin usage against:
- Pin map comments in source files.
- README or documentation references.
- Schematic references if available.
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.
- 12d ago First seen · 100 lines · 22 tokens per session scan A 271a2129e84b
esp32_pin_audit is a skill published in the GitHub repository agodianel/esp32-claude-workbench (79 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 752 once invoked, about $0.0001 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.