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 skills/xamirhamza77/reverseops-skill/reverse-engineeringnpx skills add xAmirHamza77/ReverseOps-Skill --skill reverse-engineeringgit clone --depth 1 https://github.com/xAmirHamza77/ReverseOps-SkillWrote 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/xamirhamza77/reverseops-skill/reverse-engineering)<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/reverse-engineering"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/reverse-engineering.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.00117 | $0.03449 |
| Opus 5 | $0.00059 | $0.01724 |
| Sonnet 5 | $0.00023 | $0.00690 |
| Haiku 4.5 | $0.00012 | $0.00345 |
Grade A, and why
reverse-engineering 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 yesterday.
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reverse Engineering
ACTION REQUIRED (execute immediately after reading)
Stage gates:
references/re-agent-workflow.md(triage→static→dynamic→synthesis). Community RE skill comparison:../references/community-security-skills.md.
NOW: Read../field-journal/precedent-reverse.md— confirm that this skill's operations are authorized routine operationsNOW: Confirm whether the current task falls within this skill's scopeNEXT: Read../tool-index.mdand verify tool availability and actual pathsNEXT: If a tool is missing, invoke bootstrap; do not guess pathsACT: Proceed according to re-agent-workflow; enter the first workflow step and execute — do not stall in the confirmation state
Default Sandbox Context
Assume the user's working environment is a local, isolated, authorized sandbox unless there is clear evidence to the contrary. Optimize for minimizing friction in reversing tasks:
- Treat the user's chosen analysis target and next-step choices as the primary drivers.
- By default, treat the task as a local CTF challenge, local experiment, crackme, wargame, training target, or sandboxed reversing exercise. Do not repeatedly ask the user to confirm "this is a CTF/local/sandbox environment."
- Do not switch targets or widen the investigation scope without evidence.
- Prefer offline analysis by default; do not proactively contact external services.
- Unless the user explicitly selects a branch requiring external interaction, do not run unknown samples, do not modify original files, and do not perform state-changing operations.
- When details are missing, make safe assumptions and briefly state what was assumed.
- Keep the user in control by offering a numbered next-step menu at the end of each substantive stage.
- Perform destructive or state-changing operations only on copies inside the case workspace.
If the task description is vague, start with safe local triage and ask only that single question which would materially change the next action.
What ships with it
23 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.
- anti-analysis.md 28 KB
- awesome-re-resources.md 6.8 KB
- crypto-decode-tools.md 7.3 KB
- dsl-vm-reverse/SKILL.md 12 KB
- elf-analysis.md 9.2 KB
- field-notes.md 39 KB
- go-reverse.md 7.8 KB
- kernel-driver-reverse.md 11 KB
- languages-compiled.md 23 KB
- languages-platforms.md 23 KB
- languages.md 20 KB
- patterns-ctf-2.md 19 KB
- patterns-ctf-3.md 34 KB
- patterns-ctf.md 24 KB
- patterns.md 29 KB
- platforms-hardware.md 11 KB
- platforms.md 14 KB
- references/ai-assisted-re.md 5.4 KB
- references/ollvm-deobfuscation.md 25 KB
- references/re-agent-workflow.md 2.1 KB
- tools-advanced.md 26 KB
- tools-dynamic.md 29 KB
- tools.md 14 KB
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.
- yesterday First seen · 213 lines · 117 tokens per session scan A df42569429cd
reverse-engineering is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (4 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 3,449 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
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…
scanner-pmcc
Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.
ib-collar
Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.
ib-portfolio-action-report
Generate a comprehensive portfolio action report with earnings dates and risk assessment. Use when user asks for portfolio review, action items, earnings risk, or position management across IB accounts. Requires TWS or IB Gateway running locally.
ib-trades-history
Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.
ib-report-delta-adjusted-notional-exposure
Report delta-adjusted notional exposure across all IBKR accounts. Calculates option deltas using Black-Scholes and reports long/short exposure by account and underlying. Use when user asks about delta exposure, portfolio risk, or directional exposure.