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 skills add xAmirHamza77/ReverseOps-Skill --skill binary-diffgit 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/binary-diff)<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/binary-diff"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/binary-diff/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.
<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/binary-diff"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/binary-diff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00129 | $0.03133 |
| Opus 5.5 | $0.00052 | $0.01253 |
| Sonnet 5.5 | $0.00026 | $0.00627 |
| Haiku 4.5 | $0.00013 | $0.00313 |
Grade A, and why
binary-diff 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 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.
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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Version Symbol Migration (Binary Diff)
ACTION REQUIRED (execute immediately after reading)
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 scope of applicabilityNEXT: Read../tool-index.mdto verify tool availability and actual pathsNEXT: If tools are missing, invoke bootstrap; do not guess pathsACT: Enter the first step of the "Workflow" and execute; do not stall in the confirmation state
Scope of Applicability
Use this skill when the task falls into one of the following scenarios:
- Kernel/driver missing PDB — You have symbols for an old ntoskrnl.exe, the new PDB has been pulled by Microsoft, and you need to derive new-version non-exported function addresses from old-version symbols
- Symbol migration after a program update — You previously reverse engineered a program, the program was updated, and instead of reversing it all over again, you want to batch-migrate the old results
- Protection mechanism update — The old version has complete reverse engineering results, and you need to quickly locate the new offsets of the same functions
- Any binary comparison scenario involving "old version with symbols + new version without symbols"
Division of labor with other skills
| Scenario | What to use |
|---|---|
| Reverse engineering a binary from scratch | ida-reverse/ or radare2/ |
| Have old-version results, migrate to new version | This skill |
| Comparing two completely different binaries | BinDiff / Diaphora (traditional tools) |
Core advantages
Compared with traditional approaches:
| Approach | Cost for 200 functions | Time | Accuracy |
|---|---|---|---|
| Manual comparison with two IDA windows open | Free but draining | Several hours | High |
| BinDiff automatic matching | Free | Fast | Medium (fails with large structural changes) |
| Fully delegated to an Agent (CC/Codex) | 50-100 yuan | Slow | High |
| This skill (LLM batch comparison) | ~1 yuan | ~10 sec/function | High |
What ships with it
1 file 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.
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 · 315 lines · 129 tokens per session scan A 2925057ed688
binary-diff is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (5 stars, last pushed 2mo ago), licensed MIT. It adds 129 tokens to every session and 3,133 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
fix-my-app
Find and fix a problem in a Taskade Genesis app, change one thing at a time, and prove the change with the file contents. Use when the user says "my Taskade app is broken", "fix my app", "the page is blank", "the button does nothing", "data does not show in my app", or asks to change text, layout or a field in their…
interacting-with-project-runtime
Interacting with a project's JVM runtime through the Kotlin REPL to execute focused probes against project classes and dependencies. Activate when behavior must be observed by running code; use using-gradle for build inspection or task execution.
using-gradle
Using Gradle MCP tools to inspect and run existing builds, including projects, tasks, properties, dependencies, and build results. Activate for Gradle build operation and diagnosis; use authoring-gradle-builds when the build definition itself must change.
browser-debug
Debug style issues and console errors in a running web app using the kogiQA browser tools. Use when asked to investigate a layout/overflow problem, a broken page, or to collect and fix console errors.
debug-helper
Systematic debugging approach for identifying and fixing issues.
error-handling
Read the error codes these tools raise and decide whether to retry, fix the call, or stop.