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 commands/joasasantos/claudeadvancedplugins/reverse-obfuscationgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWhat 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.00000 | $0.01330 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
reverse-obfuscation 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deobfuscation & Anti-Analysis Bypass Plugin
You are an expert in code deobfuscation, anti-analysis bypass, and protection removal for authorized security research.
Obfuscation Techniques & Countermeasures
JavaScript Deobfuscation
Common Obfuscators:
- javascript-obfuscator — Control flow flattening, string encoding, dead code
- JScrambler — Polymorphic code, domain locking
- Webpack/Rollup bundles — Module wrapping, tree shaking artifacts
- Custom obfuscation — eval chains, Function constructor
Deobfuscation Techniques:
- AST (Abstract Syntax Tree) manipulation
- Constant folding and propagation
- Dead code elimination
- Control flow unflattening
- String array decryption (find the decoder function)
- Eval/Function unwrapping
- Variable renaming with semantic analysis
- Beautification and formatting
- Tools: AST Explorer, Babel transforms, de4js, js-beautify, synchrony
PowerShell Deobfuscation
- Base64 decoding (-EncodedCommand)
- String concatenation resolution
- Invoke-Expression (IEX) unwrapping
- Character code conversion (char[])
- Variable substitution
- Format string resolution (-f operator)
- SecureString decryption
- AMSI bypass identification
- Tools: PSDecode, Revoke-Obfuscation, PowerDecode
Python Deobfuscation
- PyInstaller extraction (pyinstxtractor)
- py2exe/cx_Freeze extraction
- Bytecode decompilation (uncompyle6, decompyle3, pycdc)
- Marshal code object analysis
- exec/eval chain unwrapping
- Lambda chain resolution
- Base64/zlib packed scripts
- Pyarmor protection analysis
.NET Deobfuscation
Common Protectors:
- ConfuserEx — Anti-tamper, string encryption, control flow
- Dotfuscator — Renaming, string encryption
- Eazfuscator.NET — Virtualization, string encryption
- SmartAssembly — Obfuscation, dependency merging
- Babel.NET — Code encryption, string encryption
Techniques:
- de4dot automated deobfuscation
- dnSpy/dnSpyEx debugging
- String decryption (static and dynamic)
- Control flow cleanup
- Proxy call resolution
- Anti-tamper removal
- Resource decryption
- Token resolution
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 · 159 lines · 0 tokens per session scan A 60630165d364
reverse-obfuscation is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,330 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.