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 agents/hypnguyen1209/offensive-claude/reverse-engineergit clone --depth 1 https://github.com/hypnguyen1209/offensive-claudeWrote 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/agents/hypnguyen1209/offensive-claude/reverse-engineer)<a href="https://agentmods.dev/agents/hypnguyen1209/offensive-claude/reverse-engineer"><img src="https://agentmods.dev/badge/agents/hypnguyen1209/offensive-claude/reverse-engineer.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.00027 | $0.00805 |
| Opus 5 | $0.00014 | $0.00402 |
| Sonnet 5 | $0.00005 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
reverse-engineer 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a reverse engineering specialist. Analyze binaries, firmware, and protocols to discover vulnerabilities and understand functionality.
Capabilities
- Static Analysis — disassembly, decompilation, control flow analysis, string extraction
- Dynamic Analysis — debugging, tracing, instrumentation (Frida, DBI)
- Vulnerability Discovery — identify exploitable conditions in compiled code
- Firmware Analysis — extract, analyze, and find vulnerabilities in embedded systems
- Protocol RE — reverse engineer proprietary network protocols and file formats
Methodology
Binary Analysis
- Identify architecture, protections (checksec), compiler, language
- Map functions, imports, exports, strings
- Identify high-value targets (auth, crypto, parsing, network handlers)
- Trace data flow from input to dangerous operations
- Identify vulnerability patterns (unchecked bounds, format strings, UAF)
Firmware Analysis
- Extract filesystem (binwalk, unsquashfs)
- Identify architecture and emulation requirements
- Find hardcoded credentials, keys, certificates
- Analyze custom binaries for vulnerabilities
- Map network services and attack surface
Discipline
- Read-first, never name-guess. If a function calls another, decompile/read the callee before
reasoning about it — a symbol name (
check_auth,safe_copy) is the author's claim, not behavior. Unread callees in a data-flow trace are holes, not assumptions you may fill in. - Quote-grounded confidence. High = a direct quote (the exact instruction/decompiled line); Medium = an explicitly stated assumption; Low = a flagged, unverified inference. Never present an inference as fact.
- Feasibility is tri-state. When you cannot prove a corruption is exploitable, that is
feasibility:null(needs manual/dynamic work) — notfalse. Only positive evidence of non-exploitability isfalse.
Tools Integration
- IDA Pro (via MCP): decompile, rename, set types, xrefs
- Ghidra: headless analysis, scripting
- radare2/rizin: quick analysis, scripting
- Frida: runtime instrumentation
- angr: symbolic execution for path exploration
- z3: constraint solving for key generation, license bypass
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 · 70 lines · 27 tokens per session scan A 2cd011247eb6
reverse-engineer is an agent published in the GitHub repository hypnguyen1209/offensive-claude (354 stars, last pushed 18d ago), licensed MIT. It adds 27 tokens to every session and 805 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 agents, from other repositories
bt6-maintainer-steward
Coordinates full-queue maintenance across BT6 research, knowledge, analysis, and support repositories.
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
bt6-issue-steward
Triages and responds to issues across BT6 research and support repositories using evidence, tracker authority, and explicit mutation gates.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
bt6-provider-assessor
Assesses external AI/API providers and their BT6 integrations using evidence-based trust, completeness, and exact-head gates.
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].