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/xamirhamza77/reverseops-skill/dotnet-reversenpx skills add xAmirHamza77/ReverseOps-Skill --skill dotnet-reversegit clone --depth 1 https://github.com/xAmirHamza77/ReverseOps-SkillWhat 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.00132 | $0.02734 |
| Opus 5 | $0.00066 | $0.01367 |
| Sonnet 5 | $0.00026 | $0.00547 |
| Haiku 4.5 | $0.00013 | $0.00273 |
Grade A, and why
dotnet-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 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET / C# Reverse Engineering Standard Operating Procedure
ACTION REQUIRED (execute immediately after reading)
NOW: Use DIE/file/CLR header to confirm the target is managed .NET (otherwise SWITCH toida-reverse//reverse-engineering/)NOW: If obfuscation is suspected → runde4dotfirst to unpack, produce*-clean.exe, and preserve the original sampleNEXT: Static analysis with dnSpyEx (or dnSpy MCP /ilspycmd): browse C# + use the IL view for key decision logicACT: Debug dynamically when plaintext/C2 is needed; when logic changes are needed, prefer IL patching over C# recompilation- At the end of each phase, give the user a 3–6 item next-step menu (including report export)
Scope
Prefer this skill when the task involves:
- Identifying and reversing .NET / C# compiled artifacts (managed PE / .exe / .dll)
- Analyzing red team Sharp* toolchains (Rubeus, SharpHound, SharpShell, etc.)
- Deobfuscating ConfuserEx / SmartAssembly / Babel / Eazfuscator / .NET Reactor and similar protectors
- Reversing the decryption and C2 logic of .NET loaders / info-stealers / RATs
- Patching C# programs (modifying checks, constants, keygen)
- Analyzing the pre-IL2CPP Mono/Unity managed layer (note: after IL2CPP compilation it is native; use
reverse-engineering/+ seed-014)
If the target is a pure native binary (compiled C/C++/Go/Rust, no CLR), use reverse-engineering/, ida-reverse/, or radare2/ instead.
Core Principles
- Identify before acting: Confirm it is a managed .NET program first (CLR in the PE header +
#~/#Stringsstreams + mscoree_CorExeMain), then decide to use dnSpy instead of IDA - IL over C#: dnSpyEx's C# decompiler can lose/distort information (compiler-generated state machines, async/await, yield); key decision logic and patches must be done in the IL editor. The C# view is only for quick browsing
- de4dot first: When an obfuscator is encountered, run
de4dotfirst before static analysis; otherwise strings/control flow are all garbage - MCP integration: If a dnSpy MCP (
dnspy_*tools) is registered in the environment, prefer the MCP interface for decompilation / IL inspection to avoid switching back and forth to the GUI - Evidence-based output: Deobfuscated artifacts, extracted configs/C2/keys, and patch diffs must all be written to disk
What ships with it
3 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.
- 2d ago First seen · 193 lines · 132 tokens per session scan A 7e1840930381
dotnet-reverse is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (4 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 2,734 once invoked, about $0.0007 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
mcpfusion-development
How to build production MCP servers with MCP Fusion using the MVA (Model-View-Agent) pattern. Use this skill whenever writing, modifying, or reviewing MCP Fusion code — including tools, Presenters, Models, middleware, prompts, routers, tests, or server configuration. Activate even when the user just says "create a…
vinkius-deploy
How to deploy MCP servers to Vinkius Edge using mcpfusion deploy. Use this skill whenever deploying, configuring remote settings, preparing an entrypoint for edge deployment, or troubleshooting deploy-related errors. Activate when the user says "deploy", "publish to edge", "mcpfusion deploy", "push to Vinkius"…
verifying-compose-ui
Verifying Compose UI by rendering components or previews and inspecting the resulting images and state transitions. Activate for visual behavior that requires runtime rendering; use ordinary tests for nonvisual logic.
raindrop-mcp-publishing
Automates and manages the complete publishing workflow for @adeze/raindrop-mcp from version bumping through npm registry deployment.
mcp-testing
MCP Testing Strategies with Vitest, Inspector, and Integration Tests.
publishing
Publishing and release workflow with semantic-release and GitHub Actions.