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 agentmods add skills/easyzoom/aix-skills/hardware-interface-debugnpx skills add easyzoom/aix-skills --skill hardware-interface-debuggit clone --depth 1 https://github.com/easyzoom/aix-skillsWrote 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/easyzoom/aix-skills/hardware-interface-debug)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/hardware-interface-debug"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/hardware-interface-debug.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 | $0.00034 | $0.00811 |
| Opus 5 | $0.00017 | $0.00405 |
| Sonnet 5 | $0.00007 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
hardware-interface-debug 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 4d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardware Interface Debug
Overview
Use this skill when firmware symptoms may actually come from board-level signals. Verify power, reset, clocks, pin mapping, voltage levels, and measured waveforms before treating the issue as a software bug.
When To Use
Use this skill when:
- The issue involves power rails, reset, crystals, boot pins, connectors, level shifters, pull-ups, or signal integrity.
- A peripheral or debug interface has no signal, wrong voltage, ringing, stuck line, or intermittent behavior.
- The user has a schematic, board photo, oscilloscope capture, logic analyzer trace, or pinout question.
Do not use this skill when the hardware path has already been verified and the issue is clearly inside firmware logic.
First Questions
Ask for:
- Board/chip, revision, and affected interface.
- Schematic snippet or pin mapping if available.
- Expected signal and observed measurement.
- Measurement tool: multimeter, oscilloscope, logic analyzer, current probe.
- Power source and voltage levels.
- Whether the issue is reproducible across boards.
Workflow
-
Start with power and ground. Confirm rail voltage, sequencing, ripple, current limit, ground reference, and target voltage for debug probes.
-
Check reset and clock. Verify reset release, boot strap states, oscillator startup, clock output, and brownout/watchdog conditions.
-
Trace the signal path. Map MCU pin, package pin, board net, connector, level shifter, external device, and pull components.
-
Measure at the right points. Compare near-MCU and near-peripheral signals to catch level shifter, connector, or routing issues.
-
Compare against firmware configuration. Pin mux, open-drain/push-pull, drive strength, alternate function, and analog mode must match the hardware.
-
Avoid destructive experiments. Do not short pins, force rails, remove protections, or bypass regulators without explicit user approval.
Signal Checks
- Voltage level matches both devices.
- Ground reference is shared.
- Pull-up/down values are appropriate.
- Rise/fall time fits bus speed.
- No two outputs fight on the same net.
- Boot strap resistors match intended mode.
- Debug pins are not overloaded by external circuits.
- Reset pulse width and polarity match datasheet.
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.
- 4d ago First seen · 102 lines · 34 tokens per session scan A 5101efe92367
hardware-interface-debug is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 811 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
embedded-debugging
Debug embedded firmware on real hardware through the jlink-mcp server — crashes, hangs, peripheral misconfiguration, silent devices. Covers loading ELF symbols for source-level backtraces, supplying an SVD for named peripheral fields, and the halt/read/resume discipline. Use whenever debugging a microcontroller over a…
prompt-transparency
Inspired by the CL4R1T4S project (github.com/elder-plinius/CL4R1T4S), this skill audits and surfaces all implicit behavioral instructions, system prompts, and agent directives embedded in this repository. It generates a human-readable transparency report so anyone can understand exactly how the AI agents in this repo…
system-prompt-audit
Audit all system-level instructions embedded in this repository's Claude configuration, surface them as a structured inventory, and validate them for consistency, safety, and alignment with project goals.
figma-to-coded-html
Convert Figma designs into self-contained, shareable single-file HTML with all UI elements coded in HTML/CSS/SVG and only actual photographs embedded as inline base64. Use this skill whenever the user asks to convert a Figma file/URL to HTML, export Figma designs as code, create HTML from Figma, turn a Figma mockup…
embedded-review
Expert code review for embedded/firmware projects with dual-model cross-review (Claude + Codex via ACP). Detects memory safety, interrupt hazards, RTOS pitfalls, hardware interface bugs, and C/C++ anti-patterns. Trigger when user asks to review embedded/firmware/MCU code changes, diffs, or PRs. Examples: 'review…
ek-omniprobe-ai
通过 EK-OmniProbe 本机 TCP/NDJSON 桥接读取串口文本与标准样本、分析日志和波形，并安全调节设备参数。用户要求观察串口数据、分析诊断输出、传感器或控制波形、评估调参效果、建议 PID 等参数、自动或半自动调参时使用。.