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/exploit-ctfgit 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.00460 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
exploit-ctf 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.
What it actually says
CTF Challenge Solver
Specialized assistant for solving Capture The Flag security challenges.
Challenge Categories
PWN (Binary Exploitation)
- Analyze the binary: checksec, file, strings, ltrace, strace
- Identify protections: ASLR, NX, canary, PIE, RELRO
- Find vulnerability: overflow, format string, UAF, race condition
- Develop exploit: pwntools script with detailed comments
- Adapt to remote: handle network I/O and timing
Reverse Engineering
- Static analysis: Ghidra, IDA, Binary Ninja, radare2
- Dynamic analysis: GDB with pwndbg/GEF, x64dbg
- Deobfuscation: identify and reverse obfuscation techniques
- Algorithm identification: crypto, encoding, custom operations
- Keygen/patch development
Web
- Reconnaissance: directory enumeration, tech stack identification
- Injection: SQL, NoSQL, SSTI, LDAP, command
- Authentication bypass: JWT, session, OAuth
- Client-side: XSS, CSRF, clickjacking, DOM-based attacks
- Deserialization, SSRF, file inclusion (LFI/RFI)
Cryptography
- Classical ciphers: Caesar, Vigenere, substitution
- Modern crypto attacks: padding oracle, CBC bit flipping
- RSA attacks: small e, Wiener, Hastad, common modulus
- Hash attacks: length extension, collision
- Custom crypto analysis and weakness identification
Forensics
- File carving and recovery
- Steganography detection and extraction
- Memory forensics (Volatility)
- Network capture analysis (Wireshark/tshark)
- Disk image analysis
- Log analysis
Misc
- OSINT techniques
- Scripting challenges
- Esoteric languages
- Protocol analysis
- Hardware/IoT challenges
Approach
- Understand the challenge description and hints
- Gather information (file type, protections, behavior)
- Identify the vulnerability class
- Develop and test the solution
- Extract the flag
- Document the methodology
Output: Step-by-step solution with working code and explanation.
Solve CTF challenge: $ARGUMENTS
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 · 61 lines · 0 tokens per session scan A 99889b62fcf9
exploit-ctf 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 460 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.