reverse-engineering-lord

reverse-engineering-lord is a skill for Claude Code, Codex from m3taz-ahmed/ai-globals. It costs 82 tokens per session (1,470 once invoked), scanned A, original, MIT.

A reverse-engineering guide for examining shipped software and hardware artifacts such as binaries, packages, mobile apps, firmware, and assemblies. It uses REA tools and separates direct observations from conclusions and unknowns.

In plain words
What is it for?
Use it to inspect, compare, decompile, or reconstruct native programs, Electron or JavaScript apps, .NET assemblies, APKs, firmware, and packages with supported analysis tools.
Why use it?
It helps investigate behavior when source code is unavailable or does not explain what a shipped artifact does. Read-only work is the default, and the guide avoids reverse-engineering when ordinary source analysis is enough.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it to inspect, compare, decompile, or reconstruct native programs, Electron or JavaScript apps, .NET assemblies, APKs, firmware, and packages with supported analysis tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/m3taz-ahmed/ai-globals/reverse-engineering-lord
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.

Any agent
npx skills add m3taz-ahmed/ai-globals --skill reverse-engineering-lord
Clone the repo
git clone --depth 1 https://github.com/m3taz-ahmed/ai-globals

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.

agentmods badge for reverse-engineering-lord

README.md
[![agentmods](https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/reverse-engineering-lord/github.svg)](https://agentmods.dev/skills/m3taz-ahmed/ai-globals/reverse-engineering-lord)
Your own site
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/reverse-engineering-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/reverse-engineering-lord/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.

agentmods 80×15 button for reverse-engineering-lord

Your own site · 80×15
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/reverse-engineering-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/reverse-engineering-lord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,470 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.01470
Opus 5.5 $0.00033 $0.00588
Sonnet 5.5 $0.00016 $0.00294
Haiku 4.5 $0.00008 $0.00147

Measured 4d ago against content hash 49ba62e6a56b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

reverse-engineering-lord 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.

skills/reverse-engineering-lord/SKILL.md · 62 lines

How it starts

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

Reverse Engineering Lord

[SKILL] reverse-engineering-lord [OBJ] Explain, compare, decompile, or reconstruct shipped artifacts with REA (rea-agents CLI/MCP server). Compressed doctrine adapted from morluto/rea (MIT) .agents/skills/reverse-engineer-anything.

[RULES]

  1. [REQ] When to Use — Only when a claim depends on a shipped binary/package, decompilation, runtime evidence, or behavior NOT established by available source. Ordinary source-repo analysis → normal repo tools, never REA.
  2. [REQ] Connect Only When Needed — REA tools available → proceed directly; NEVER run doctor/setup before every investigation. Absent tools → diagnose the exact blocker (missing registration vs stale session vs missing provider) with npx -y rea-agents@latest doctor --client <client> --json (clients: claude_code, codex, cursor, gemini_cli, windsurf, devin, vscode…), repair scoped, restart agent, resume task.
  3. [REQ] Setup Discipline — Configuration repair starts with a read-only plan: npx -y rea-agents@latest setup --client <client> --dry-run --json; show proposed paths + backups + skill replacement; apply --yes only after approval. rea setup NEVER installs/upgrades Node, npm, Java, Ghidra, IDA, JADX, Kuna, Binwalk, Unblob — bring-your-own engines only.
  4. [REQ] Route the Target First — Pick the first tool from the supplied target: extracted JS/Electron tree or ASAR → analyze_javascript_application; archive members (ZIP/APK/IPA/DMG/PyInstaller) → open_binary (detail: "summary" first for large inventories); Apple plist/assets → open_bundle_resources; APK code/classes → inspect_android_package; .NET PE/CLI → inspect_managed_artifact; firmware → inspect_firmware_regions; open browser page → list_browser_targets. Runtime options are metadata, not files.
  5. [REQ] Evidence Discipline — Distinguish observation / derivation / inference / unknown in every report. Preserve provenance (paths, digests, offsets, source locations). Unresolved identity or applicability stays UNKNOWN — never treated as absent or aligned. Keep complete inline Evidence when the server does not advertise retained references.
  6. [REQ] Read-Only Authority — Ghidra uses ephemeral DBs without modifying executable bytes; IDA analysis is read-only (never save/close an attached GUI DB); no mutation authority on Windows Ghidra P0. Fail closed: skip capabilities while scope/authority/side-effect questions are unresolved.
  7. [REQ] Local Checkout First — A full REA source checkout is installed OUTSIDE this repo: resolve $REA_HOME, else sibling ../rea next to the aizee root (tech-stack/useful-repos.md is the registry). Invoke through the engine-aware wrapper node ../rea-cli.mjs <command> /abs/path --json (sibling rea-cli.mjs next to the aizee root — it pins the checkout's .nvmrc Node under NVM_HOME and injects GHIDRA_INSTALL_DIR/JAVA_HOME); plain node "$REA_HOME/scripts/rea.mjs" also works for engine-free tasks; npx -y [email protected] is the last resort. All return the same Evidence record, no MCP needed for static JS/.NET/artifact work. Native targets still require their selected engine (Hopper/Ghidra/IDA); a CLI fallback does NOT prove MCP registration. NEVER edit files inside the checkout; refresh it with git -C <checkout> pull && npm ci && npm run build:cached under the pinned Node. Missing dist/ → run npm ci && npm run build:cached inside the checkout before use.
  8. [REQ] Timeout Handling — Host timeout without a result ≠ work stopped; check provider startup deadline (REA_GHIDRA_STARTUP_TIMEOUT_MS/REA_HOPPER_STARTUP_TIMEOUT_MS for large binaries) before retrying an unchanged call.
  9. [PROHIBIT] Never repeat an unchanged call after a timeout or assume an absent provider blocks unrelated targets — static JavaScript inspection needs neither Hopper nor Ghidra.
  10. [PROHIBIT] Never run target binaries, inject, mutate, or recover protections beyond declared scope — those need an explicit user scope decision first.
  11. [PROHIBIT] Never claim runtime reproduction you did not perform; label hypotheses and unverified coverage explicitly (NOT_ENOUGH_INFO beats a confident guess).
  12. [CMD] Providers — deep native: Hopper/Ghidra/IDA/Kuna/JEB + objdump/rizin/cutter/GDB; mobile: JADX/Apktool/adb; web: Chrome CDP/Playwright, HAR/SAZ captures; formats: WABT (wasm), tshark (pcap), sigrok (signals), binwalk/unblob (firmware), pwntools/GDB (ELF/coredumps). All caller-supplied.

Read the full file on GitHub · 62 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. 4d ago First seen · 62 lines · 82 tokens per session scan A 49ba62e6a56b

Subscribe to this mod's changes

reverse-engineering-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,470 once invoked, about $0.0003 per session on Opus 5.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-10-24.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens