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 0dayInc/pwn --skill hardware-and-firmware-testinggit clone --depth 1 https://github.com/0dayInc/pwnWrote 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/0dayinc/pwn/hardware-and-firmware-testing)<a href="https://agentmods.dev/skills/0dayinc/pwn/hardware-and-firmware-testing"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/hardware-and-firmware-testing/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/0dayinc/pwn/hardware-and-firmware-testing"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/hardware-and-firmware-testing.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.00024 | $0.00714 |
| Opus 5 | $0.00012 | $0.00357 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
hardware-and-firmware-testing 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardware and Firmware Testing
Use when the target is a device, PCB, UART/JTAG, RF dongle, or a firmware
image. Hand unpacked binaries to reverse-engineering-binaries and
crashes to deep-exploitation.
When to use
- firmware dump, IoT, router image, MCU flash
- UART / SPI / I2C / JTAG / SWD
- RF / SDR path (
PWN::SDR,pwn_gqrx_scanner)
Methodologies
OWASP Firmware Security Testing Methodology (FSTM) - 9 stages:
- Information gathering
- Obtaining firmware
- Analyzing firmware
- Extracting the filesystem
- Analyzing filesystem contents
- Emulating firmware
- Dynamic analysis
- Runtime analysis
- Binary exploitation
Also:
| Catalog | Role |
|---|---|
| OWASP ISTG | IoT device test cases (firmware chapter cites FSTM) |
| OSSTMM | physical + wireless + telecom channels |
| NIST SP 800-115 | evidence and reporting |
| CWE | 119, 798, 1278, 1326 for embedded flaws |
Tooling
- Hardware:
PWN::Plugins::Serial,BusPirate,Android(adb),MSR206when magstripe is in the ask - RF:
PWN::SDR,pwn_gqrx_scanner, Flipper helpers in SDR docs - Extract:
binwalk,sasquatch/unsquashfs,firmware-mod-kitif present - RE:
file,strings,radare2,PWN::Plugins::Assembly - Emulate: QEMU user/system when the arch is known
Procedure
- FSTM-1: chip markings, FCC ID, model, debug headers. Photograph or note.
- Obtain the image (vendor download, dump via UART/flash). Hash it.
binwalk -e, list filesystems, creds, keys, init scripts.- Emulate or boot if possible. Dynamic: default creds, open ports, update channel.
- Runtime: attach serial, check root shell, busybox, leftover test hooks.
- Binary: pick one sink, then
reverse-engineering-binaries/deep-exploitation. - Report per FSTM stage with artefact paths.
Pitfalls
stringson a blob is not FSTM-complete.- Do not brick the only sample. Prefer a copy / emulator.
- RF work stays on the named band/profile.
Verification
Image hash + extract dir exist, at least two FSTM stages have evidence beyond notes, and leftover secrets or sinks are cited from files that were read back.
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 · 84 lines · 24 tokens per session scan A f3bcf17eea79
hardware-and-firmware-testing is a skill published in the GitHub repository 0dayInc/pwn (82 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 714 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
race
Race condition / TOCTOU playbook — limit overrun (one-time codes used twice, gift cards spent twice), single-packet attack (last-byte sync) to force parallel processing, and state-confusion races (file upload + read, order before payment). Use when timing-sensitive logic could be abused — one-time codes, coupons/gift…
syzkaller-ppdev-syzlang
Syzkaller is a coverage-guided kernel fuzzer. To fuzz a device driver, you must describe its syscall interface in syzlang — syzkaller's domain-specific language. This skill covers the full workflow: reading kernel headers, computing ioctl numbers, writing .txt (syzlang) and .txt.const (constants) files, and verifying…
exploiting-insecure-deserialization
Identifying and exploiting insecure deserialization vulnerabilities in Java, PHP, Python, and .NET applications to achieve remote code execution during authorized penetration tests.
testing-for-business-logic-vulnerabilities
Identifying flaws in application business logic that allow price manipulation, workflow bypass, and privilege escalation beyond what technical vulnerability scanners can detect.
testing-for-sensitive-data-exposure
Identifying sensitive data exposure vulnerabilities including API key leakage, PII in responses, insecure storage, and unprotected data transmission during security assessments.
recon
External recon playbook for a web target — subdomain enumeration, live-host probing, tech fingerprinting, and a first pass at content discovery. Use when the user gives you a root domain or apex and wants attack surface mapping.