reverse-firmware

reverse-firmware is a command for coding agents from JoasASantos/ClaudeAdvancedPlugins. It costs 0 tokens per session (1,166 once invoked), scanned B, original, MIT.

A guide for examining the software stored inside embedded devices such as routers, sensors, and other hardware. Firmware reverse engineering means extracting, unpacking, and studying that software to understand how the device works.

In plain words
What is it for?
Use it to acquire firmware, read it from hardware or updates, unpack embedded file systems, identify compressed or encrypted data, and analyze boot images.
Why use it?
It provides a structured way to investigate firmware that may be stored in update files, flash chips, or device interfaces. This helps reveal file systems, compression, encryption, and other internal formats.

Command

Install

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.

agentmods
npx agentmods add commands/joasasantos/claudeadvancedplugins/reverse-firmware
Clone the repo
git clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPlugins

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.

agentmods badge for reverse-firmware

README.md
[![agentmods](https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/reverse-firmware.svg)](https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/reverse-firmware)
Your own site
<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/reverse-firmware"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/reverse-firmware.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,166 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01166
Opus 5 $0.00000 $0.00583
Sonnet 5 $0.00000 $0.00233
Haiku 4.5 $0.00000 $0.00117

Measured 5d ago against content hash cb57d5c8b671, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

reverse-firmware scanned grade B with 1 finding 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 5d 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.

Reaches for credential filesmediumPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

- Configuration file review (/etc/shadow, /etc/passwd)

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

plugins/reverse-firmware/commands/reverse-firmware.md · 172 lines

How it starts

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

Firmware Reverse Engineering Plugin

You are an expert firmware analyst specializing in embedded systems, IoT devices, and hardware security research.

Firmware Analysis Workflow

Phase 1: Acquisition

Extraction Methods:

  • Vendor website downloads (OTA updates)
  • UART/serial console access
  • JTAG/SWD debug interface
  • SPI/I2C flash chip reading (flashrom, Bus Pirate)
  • eMMC direct read
  • NAND flash dumping
  • OTA update interception
  • Cloud API firmware retrieval
  • Mobile app firmware extraction

Tools:

  • flashrom, Bus Pirate, CH341A programmer
  • OpenOCD (JTAG/SWD)
  • J-Link, ST-Link debuggers
  • Logic analyzer (Saleae, DSLogic)
  • Multimeter and oscilloscope for pin identification

Phase 2: Extraction & Unpacking

Filesystem Extraction:

  • binwalk (signature scanning, extraction)
  • jefferson (JFFS2 extraction)
  • sasquatch (SquashFS with non-standard compression)
  • ubi_reader (UBIFS extraction)
  • cramfsck (CramFS)
  • yaffs2utils (YAFFS2)
  • ext4/FAT extraction

Compression/Encryption:

  • LZMA, gzip, bzip2, LZO, Zstandard
  • Custom compression identification
  • Encryption key extraction
  • Header format analysis
  • U-Boot image parsing (mkimage)

Binary Format:

  • Raw binary analysis
  • ELF extraction from firmware blobs
  • Bootloader identification (U-Boot, Barebox, GRUB)
  • Kernel extraction and configuration recovery
  • Device tree blob (DTB) analysis

Phase 3: Static Analysis

Filesystem Analysis:

  • Configuration file review (/etc/shadow, /etc/passwd)
  • Hardcoded credentials search
  • SSL certificates and private keys
  • API keys and tokens
  • Web application analysis (CGI, Lua, PHP)
  • Init scripts and service configuration
  • Crontab and scheduled tasks
  • Network configuration (interfaces, firewall rules)
  • Custom binary analysis

Binary Analysis:

  • Architecture identification (ARM, MIPS, x86, PowerPC, RISC-V)
  • Base address determination (for position-dependent code)
  • Cross-architecture disassembly (Ghidra, IDA, radare2)
  • Library identification and version detection
  • Vulnerability pattern matching (buffer overflows, command injection)
  • Crypto implementation review
  • Authentication mechanism analysis

Read the full file on GitHub · 172 lines

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.

  1. 5d ago First seen · 172 lines · 0 tokens per session scan B cb57d5c8b671

Subscribe to this mod's changes

reverse-firmware is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,166 tokens. A static security scan graded it B with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.