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 dslsdzc/rev-skills --skill re-crackinggit clone --depth 1 https://github.com/dslsdzc/rev-skillsWrote 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/dslsdzc/rev-skills/re-cracking)<a href="https://agentmods.dev/skills/dslsdzc/rev-skills/re-cracking"><img src="https://agentmods.dev/badge/skills/dslsdzc/rev-skills/re-cracking/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/dslsdzc/rev-skills/re-cracking"><img src="https://agentmods.dev/badge/skills/dslsdzc/rev-skills/re-cracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.02774 |
| Opus 5 | $0.00047 | $0.01387 |
| Sonnet 5 | $0.00019 | $0.00555 |
| Haiku 4.5 | $0.00009 | $0.00277 |
Grade A, and why
re-cracking 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 9d 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.
软件破解（授权定位 / 补丁 / 注册机）
授权边界（本网关及下游技能 [[re-license]] / [[re-keygen]] / [[re-patching]] / [[re-drm]] 共同适用）
- 允许场景：授权验证分析仅限——自有/自研软件分析、获得授权的测试与审计、CTF 与研究环境（题目/沙箱样本）、厂商授权的评估目标
- 禁止：未授权软件解锁、商业软件绕过、绕过授权后分发（含补丁与注册机产物扩散）
- 动态路线权限门槛：断点观察返回值、修改环境、验证行为等动态步骤属正常逆向方法，但 Agent 自动执行前必须确认用户已说明目标归属（软件所有权 / 测试授权 / CTF·研究环境之一）——未说明则只做静态授权逻辑分析，不执行动态验证与补丁落地
完整工作流
按顺序执行；每步产物（校验点地址 / 算法伪代码 / patch 文件 / keygen 脚本）记录证据路径 + sha256（见 [[re-triage]]），供报告引用。
- 带壳判断与脱壳：[[re-anti-analysis]] —— 先判壳再动手：[[re-packer-id]] 识别（节名异常 / 熵 >7 / 导入表极小 / EP 指向非首节）。带壳先脱壳（简单壳 [[re-unpack-simple]]、强壳 [[re-unpack-advanced]]，脱壳产物 sha256 存档）；脱壳后仍有花指令 / 平坦化 / 字符串加密 → [[re-deobfuscate]]。确认无壳才进入授权定位（在壳代码里找授权函数是白费功夫，见坑 1）
- 授权定位：[[re-license]] —— 字符串 / API 交叉引用找校验函数（注册对话框 / MessageBox / 注册表读取）→ 调用图与成功/失败分支 → 算法还原（对比 / 解密 / 签名验证）→ 区分在线激活与离线校验 → 识别机器码绑定。产物：全部校验点地址 + 校验算法（不只第一个，见坑 2）
- 分派：根据校验算法性质与目标选择路径——
- 算法可逆（比较 / 变换 / 查表可逆向）→ [[re-keygen]] 写注册机（生成任意合法序列号，不修改目标文件，适合分发）
- 算法不可逆（哈希；非对称验签——私钥不可由公开验证过程推导，RSA/ECC 验证本身是公开算法，不可得的是签名生成密钥）→ [[re-patching]]（跳过验签 / 改判定分支）；需要从比较链 / 数学关系硬推序列号 → [[re-z3]] 建模可选（见坑 4）
- 只想快速绕过（不关心算法）→ [[re-patching]]（最小改动：失败跳转改成功跳转）
- 两者可同时做：patch 即时可用，keygen 长期有效
- 补丁：[[re-patching]] —— 定位 patch 点（失败跳转 jz/jnz）→ 字节修改（nop / 跳转重写）→ 校验和 / 自校验处理 → 补丁导出（二进制 diff / patch 文件）→ 多架构适配（ARM 改 B 指令等）
- 注册机：[[re-keygen]] —— 从 [[re-license]] 拿到的校验算法 → 逆推生成算法（正推 / 约束求解）→ python 实现 → 校验码 / 校验位边界处理 → 多平台 CLI 输出
- 验证：沙箱内（[[re-sandbox]]，[[platform-tips]] 最高原则）复跑——补丁版与 keygen 生成的序列号必须通过全部校验点（启动 + 功能点，见坑 2）；与未修改样本对比行为一致；产物与证据路径存档
每步结果按 [[re-triage]] 记录；注册算法指纹 / 补丁字节是 [[re-ioc]] YARA 特征来源。
何时用哪个原子技能（选择树）
按输入特征 / 目标分支：
- 样本带壳（节名异常 / 熵高 / 导入表极小）→ 先 [[re-anti-analysis]]（packer-id → unpack-* → 需要时 deobfuscate），脱壳后回到本网关第 2 步
- "序列号算法是什么 / 帮我生成注册码" → [[re-license]] 还原算法 → [[re-keygen]] 生成
- "绕过注册验证 / 解锁功能" → [[re-license]] 定位校验点 → [[re-patching]] 最小改动
- 校验算法不可逆（哈希；非对称签名——私钥不可由公开验证过程推导） → [[re-patching]]（跳过验签）；想从比较链硬推 → [[re-z3]] 建模
- 在线激活（校验含网络请求）→ [[re-license]] 区分在线 / 离线后转 [[re-protocol]] 抓包分析激活流程，本地侧按离线流程处理（见坑 3）
- 只要确认注册机制是否存在（"这程序有授权吗"）→ [[re-license]] 第 1 步即可，不进入后续
- 确认无授权机制 → 不需要本网关，转 [[re-binary-core]] 正常分析
- 目标是 DRM 内容保护（PlayReady / Widevine 许可证、内容解密）→ 非传统授权校验，转 [[re-drm]]（仅授权研究，合规边界见该技能）
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.
- 9d ago First seen · 70 lines · 94 tokens per session scan A 4189f9626937
re-cracking is a skill published in the GitHub repository dslsdzc/rev-skills (50 stars, last pushed 10d ago), licensed Apache-2.0. It adds 94 tokens to every session and 2,774 once invoked, about $0.0005 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 skills, from other repositories
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
Reverse Engineering & Binary Analysis
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
reverse-engineering-binaries-with-ghidra
Uses Ghidra to disassemble and decompile a binary, navigate to key routines via imports and strings, annotate decompiled code, and run headless scripts to automate extraction of C2, crypto, and config. Activates for requests to reverse engineer with Ghidra, decompile a binary, or script Ghidra headless analysis.
reverse-engineering-shellcode
Analyzes position-independent shellcode: disassembling raw bytes at the right architecture, recognizing PEB-walk API resolution and egg hunters, and emulating execution to recover behavior and payloads. Activates for requests to analyze shellcode, disassemble raw position-independent code, or emulate a shellcode blob.