Borrowing it
Nothing to install: this file belongs to dslsdzc/rev-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dslsdzc/rev-skills/main/.claude/skills/re-tracing/SKILL.mdgit 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-tracing)<a href="https://agentmods.dev/skills/dslsdzc/rev-skills/re-tracing"><img src="https://agentmods.dev/badge/skills/dslsdzc/rev-skills/re-tracing/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-tracing"><img src="https://agentmods.dev/badge/skills/dslsdzc/rev-skills/re-tracing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 39 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 57 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00040 | $0.01852 |
| Opus 5 | $0.00020 | $0.00926 |
| Sonnet 5 | $0.00008 | $0.00370 |
| Haiku 4.5 | $0.00004 | $0.00185 |
Grade B, and why
re-tracing scanned grade B with 1 finding 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- 验证: `sudo dtruss -c ls / 2>&1 | head` 输出去重调用统计 How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
系统调用/函数调用跟踪
何时使用 / 何时不用
- 用：观察程序运行行为（文件/网络/进程操作）；记录系统调用与库调用序列作为证据；定位动态解析的 API（GetProcAddress/dlopen 之后）
- 不用：只需内存内容（走 [[re-memdump]]）；只需静态逻辑（反编译技能）
- 不用：Windows 目标用 APIMonitor/ProcMon（本技能 Linux/macOS 为主）
工具准备
参考 [[re-analyze/platform-tips]] 最高原则——跟踪即动态执行，默认在沙箱内进行，网络隔离。
strace（Linux）
- Debian/Ubuntu:
apt install strace - Fedora/RHEL:
dnf install strace - Arch:
pacman -S strace - WSL: Linux 包直接可用
- 验证:
strace -V - 常用选项：
-f跟子进程、-o写文件、-e trace=过滤、-s 200放大字符串显示（默认 32 字节）、-x非 ASCII 转十六进制、-y/-yy把 fd 解析为路径、-c汇总统计、-pattach——速查与组合见 [[commands]]
ltrace（Linux 库调用）
- Debian/Ubuntu:
apt install ltrace - Fedora/RHEL:
dnf install ltrace - Arch:
pacman -S ltrace - 验证:
ltrace -V
dtruss（macOS，DTrace 版 strace）
- macOS 自带（随 Xcode CLT）；需要 root 且部分 SIP 场景受限
- 验证:
sudo dtruss -c ls / 2>&1 | head输出去重调用统计
APIMonitor / ProcMon（Windows）
- APIMonitor: rohitab.com 下载 zip 解压即用
- ProcMon: Microsoft Sysinternals ——
choco install sysinternals（或官网下载） - 验证: 打开 APIMonitor/ProcMon 能列出并附加进程
操作步骤
-
strace -f 全进程树跟踪：
strace -f -o trace.log ./target args-f必须加：跟随 fork/vfork/clone 子进程——不加会漏掉全部子进程行为。-tt加微秒时间戳，-T加每调用耗时（网络等待/慢调用线索）；-s 200放大字符串显示（默认 32 字节，路径/参数看不全时必加）。 已运行的目标用 attach（看不到 attach 之前的调用）：sudo strace -f -p <pid> -o attach.log # attach 需要与目标同权限 strace -f -c ./target # 退出时打印系统调用计数/耗时汇总（热点定位） -
过滤（-e trace=...）：
strace -f -e trace=network,file ./target # 只看网络与文件 strace -f -e trace=write,read ./target # 只看读写 strace -f -e trace=execve,fork,clone ./target # 只看进程行为 strace -f -e trace=!futex ./target # 排除噪声（futex 高频）过滤规则先白名单后黑名单，控制输出体积（见坑 2）。
-
ltrace 库调用：
ltrace -f -o lib.log ./target ltrace -e malloc+free ./target # 只跟踪指定库函数 ltrace -l /path/libfoo.so ./target # 跟踪 dlopen 动态加载的库 ltrace -f -S ./target # 库调用 + 系统调用一起跟踪 ltrace -f -c ./target # 退出时库调用汇总动态解析的 API（
dlsym拿到的函数）不会出现在静态 IAT 里，但会出现在 ltrace 输出中——与 [[re-imports]] 互补。
What ships with it
2 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.
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.
- today Changed · +1 lines a68439438e10
- 9d ago First seen · 117 lines · 40 tokens per session scan B 91165a2680da
re-tracing is a skill published in the GitHub repository dslsdzc/rev-skills (54 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 1,852 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
Reverse Engineering & Binary Analysis
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering.
deobfuscating-powershell-obfuscated-malware
Systematically deobfuscates multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure. Use during incident response or malware analysis when a PowerShell script is obfuscated with encoding, string manipulation, or…
conducting-malware-incident-response
Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including…
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-network-covert-channels-in-malware
Detect and analyze covert communication channels used by malware, including DNS tunneling, ICMP exfiltration, steganographic HTTP, and other protocol abuse used for C2 and data exfiltration. Use when investigating suspicious DNS/ICMP/HTTP traffic patterns, hunting for hidden C2 channels in network captures, or…
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.