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/ekozmaster/vibe-reverse-engineering/dynamic-analysisnpx skills add Ekozmaster/Vibe-Reverse-Engineering --skill dynamic-analysisgit clone --depth 1 https://github.com/Ekozmaster/Vibe-Reverse-EngineeringWhat 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.00083 | $0.05582 |
| Opus 5 | $0.00042 | $0.02791 |
| Sonnet 5 | $0.00017 | $0.01116 |
| Haiku 4.5 | $0.00008 | $0.00558 |
Grade A, and why
dynamic-analysis 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 2d 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamic Analysis with livetools
For DX9 FFP proxy porting and RTX Remix compatibility, invoke the dx9-ffp-port skill.
A live analysis toolkit for running processes. Attach, trace functions, collect data, inspect state, step through code, patch memory, analyze offline -- composable tools that chain naturally for any RE scenario.
All commands: python -m livetools <command> [args]
Quick Reference
Session
python -m livetools attach <name_or_pid> # attach to running process
python -m livetools attach <exe_path> --spawn # launch + instrument before init code runs
python -m livetools detach # release target, stop daemon
python -m livetools status # check state
Breakpoints (blocking)
python -m livetools bp add <addr> # set blocking code breakpoint
python -m livetools bp del <addr> # remove breakpoint
python -m livetools bp list # list all BPs + hit counts
Wait for Hit
python -m livetools watch --timeout 60 # block until BP hit (returns snapshot)
Inspect (while frozen)
python -m livetools regs # all registers
python -m livetools stack [N] # top N dwords from ESP (default 16)
python -m livetools mem read <addr> <size> # hex dump + multi-type interpretation
python -m livetools mem read <addr> <size> --as float32
python -m livetools disasm [addr] [-n count] # disassemble (default: EIP, 16 insns)
python -m livetools bt # call stack backtrace
Supported --as types: float32, float64, half, uint8, int8, uint16, int16, uint32, int32, ptr, ascii, utf16.
Control
python -m livetools step [over|into|out] # advance one instruction (returns snapshot)
python -m livetools resume # unfreeze target
Patch + Scan (anytime)
python -m livetools mem write <addr> <hex> # write bytes to live memory
python -m livetools mem alloc <size> # allocate rwx memory in target (for code caves)
python -m livetools scan <pattern> --range START:SIZE
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.
- 2d ago First seen · 486 lines · 83 tokens per session scan A c6a657b6ee69
dynamic-analysis is a skill published in the GitHub repository Ekozmaster/Vibe-Reverse-Engineering (46 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 5,582 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…