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/uziii2208/mcp2agy/reversenpx skills add uziii2208/mcp2agy --skill reversegit clone --depth 1 https://github.com/uziii2208/mcp2agyWhat 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.00075 | $0.00845 |
| Opus 5 | $0.00037 | $0.00423 |
| Sonnet 5 | $0.00015 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade A, and why
mcp2agy-reverse 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reverse — Reverse Engineering & Binary Analysis Engine (v3.0.0)
0. Prime Directive & Operating Model
The Reverse Engineering engine reconstructs binary logic, algorithms, encryption schemes, and hidden entry points from compiled targets:
┌───────────────────────────────────┐
│ Reverse Orchestrator (/reverse) │
└─────────────────┬─────────────────┘
│
┌───────────────────┬───────────┴───────────┬───────────────────┐
▼ ▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ Static Decomp │ │ Dynamic Trace │ │ Firmware / │ │ Protocol RE & │
│(Ghidra/Radare)│ │(Frida/pwndbg) │ │ Binwalk Unpack│ │ State Machine │
└───────────────┘ └───────────────┘ └───────────────┘ └───────────────┘
│ │ │ │
└───────────────────┴───────────┬───────────┴───────────────────┘
▼
mcp2agy_workspace/reverse/analysis/<target>/
├── decompiled_annotated.c
├── symbols_map.json
├── protocol_spec.md
└── analysis_summary.md
1. Capabilities & Workflow
1.1 Static Analysis & Decompilation
- Disassembly (x86_64, ARM64, MIPS, RISC-V) via
capstoneandradare2. - Decompilation & CFG recovery via Ghidra headless scripts.
- String extraction, XOR deobfuscation, crypto constant identification.
1.2 Dynamic Instrumentation & API Hooking
- Runtime hooking of functions, parameters, and return values using
frida. - Breakpoint tracing and memory inspection in GDB (
pwndbg/gef).
1.3 Protocol & Firmware Reverse Engineering
- Automated firmware extraction via
binwalk/sasquatch. - Reverse engineering state machines and packet structures for proprietary TCP/UDP/WebSocket streams.
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 · 80 lines · 75 tokens per session scan A 5c03b8acb75f
mcp2agy-reverse is a skill published in the GitHub repository uziii2208/mcp2agy (1 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 845 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-31.
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…