What is firmware-pentest?

A workflow for examining firmware, the software stored inside routers, cameras, and other connected devices, for security weaknesses. It covers analysis, extraction, emulation, and exploit testing from firmware files.

It is for auditing router and IoT firmware, unpacking images, running them in emulators, testing services with fuzzing, and examining hardware interfaces such as UART, JTAG, and SPI.

It gives security testers a structured way to inspect device software when the physical hardware is unavailable or when testing must be automated.

firmware-pentest — Skill for Claude Code and Codex by xAmirHamza77

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/xAmirHamza77/ReverseOps-Skill

agentmods

npx agentmods add skills/xamirhamza77/reverseops-skill/firmware-pentest

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/firmware-pentest/github.svg)](https://agentmods.dev/skills/xamirhamza77/reverseops-skill/firmware-pentest)

Your own site

<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/firmware-pentest"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/firmware-pentest/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/firmware-pentest"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/firmware-pentest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 167 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,731 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00167	$0.03731
Opus 5.5	$0.00067	$0.01492
Sonnet 5.5	$0.00033	$0.00746
Haiku 4.5	$0.00017	$0.00373

Measured 1mo ago against content hash 8f8982419b9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

firmware-pentest scanned grade A with 2 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 1mo 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.

Asks for rootlowPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo emba -l ./logs -f ./firmware.bin -p ./scan-profiles/default-scan.emba

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s "https://fccid.io/?q=$FCC_ID"

skills/firmware-pentest/SKILL.md · 362 lines

How it starts

The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Firmware / IoT Pentest Chain (Firmware Pentest)

ACTION REQUIRED (execute immediately after reading)

NOW: Read ../field-journal/precedent-pentest.md — confirm that this skill's operations are authorized routine operations
NOW: Confirm whether the current task falls within this skill's scope
NEXT: Read ../tool-index.md to verify tool availability and actual paths
NEXT: When a tool is missing, invoke bootstrap; do not guess paths
ACT: Enter the first step of the workflow and execute; do not stall in the confirmation state

Scope

The following tasks enter this skill:

You have a firmware file (.bin / .img / .trx / .chk / OTA zip) and need to go from zero to RCE
Router/camera/IoT device auditing — batch discovery of known CVEs and undisclosed vulnerabilities
Encrypted/packed firmware — locate the bootloader decryption routine or perform a hardware dump
Need to run the firmware without touching hardware (QEMU full-system emulation / Firmadyne / FAT)
Fuzzing services running under emulation (AFL++ qemu mode / boofuzz)
Hardware interface access (UART / JTAG / SPI flash dump)

Division of Labor with Other Skills

Scenario	What to Use
Starting from a raw firmware file, walking the full FSTM chain	This skill
Static reversing of a single ELF/so only	`reverse-engineering/`, `ida-reverse/`, `radare2/`
Web/RCE exploitation after emulation is up	`pentest-tools/`, `attack-chain/`
Hands-on hardware interfaces (UART/JTAG/SPI)	Stage 2 section of this skill + `patterns-hardware.md`
APK / Android firmware (including boot.img)	`apk-reverse/` (strip boot.img first, then use this skill)
Cross-version firmware symbol migration	`binary-diff/`

Core Principles

Firmware .bin
   │
   ├─ Stage 1-3: Information gathering / acquisition / static analysis (what you can see without extraction)
   │
   ├─ Stage 4: Extract the filesystem  ← binwalk v3 / unblob / jefferson / ubi_reader
   │     │
   │     └─ Failure → find the bootloader decryption routine / UART dump / SPI flash hardware read
   │
   ├─ Stage 5: Filesystem static analysis  ← EMBA automation + manual grep
   │
   ├─ Stage 6: Emulated execution  ← Firmadyne / FAT / qemu-user-static + chroot
   │
   ├─ Stage 7-8: Dynamic / runtime analysis  ← gdb-multiarch, IDA remote debugging, Ghidra
   │
   └─ Stage 9: Binary exploitation  ← AFL++ fuzz / manual PoC / ARM / MIPS payload

Read the full file on GitHub · 362 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

1mo ago First seen · 362 lines · 167 tokens per session scan A 8f8982419b9f

Subscribe to this mod's changes

firmware-pentest is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (5 stars, last pushed 2mo ago), licensed MIT. It adds 167 tokens to every session and 3,731 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Hardware and IoT Security ai claude claude-skills mcp-server mcp-tools penetration-testing

building-mcp-servers

Use this skill whenever the user wants to design, build, harden, review, or debug an MCP (Model Context Protocol) server — including "build me an MCP server for X", connecting an AI agent/Claude to a database or API, adding tools/resources to an existing MCP server, reviewing a contributor PR against an MCP server, or…

cyberreinxy/mcp-server-skill · 160 tokens

lab-hardware-cad

Designs custom laboratory hardware as parametric build123d models and exports fabrication artifacts as STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a…

K-Dense-AI/scientific-agent-skills · 108 tokens

pylabrobot

Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.

K-Dense-AI/scientific-agent-skills · 49 tokens

offensive-wifi

Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…

SnailSploit/Claude-Red · 183 tokens

offensive-iot

IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential…

SnailSploit/Claude-Red · 196 tokens

offensive-bluetooth-classic

Bluetooth Classic (BR/EDR) attack methodology — device discovery, service enumeration via SDP, LMP/L2CAP layer attacks, legacy PIN cracking (BlueBorne / KNOB), Bluetooth file-transfer abuse (BlueSnarfing legacy), unauthenticated profile abuse (HSP, HFP, OPP), and modern relevance against older industrial / automotive…

SnailSploit/Claude-Red · 123 tokens

firmware-pentest