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/ctfnpx skills add uziii2208/mcp2agy --skill ctfgit clone --depth 1 https://github.com/uziii2208/mcp2agyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/uziii2208/mcp2agy/ctf)<a href="https://agentmods.dev/skills/uziii2208/mcp2agy/ctf"><img src="https://agentmods.dev/badge/skills/uziii2208/mcp2agy/ctf.svg" alt="Measured on agentmods" height="20"></a>What 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.00082 | $0.01027 |
| Opus 5 | $0.00041 | $0.00513 |
| Sonnet 5 | $0.00016 | $0.00205 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
mcp2agy-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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ctf — Autonomous Multi-Agent CTF Solving Squad (v3.0.0)
0. Prime Directive & Operating Model
The CTF engine solves competition challenges with extreme efficiency by routing challenges to dedicated specialist subagents:
┌─────────────────────────────────┐
│ CTF Lead Orchestrator (/ctf) │
└────────────────┬────────────────┘
│
┌──────────────────┬───────────┴───────────┬──────────────────┐
▼ ▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ PWN Solver │ │ REV Solver │ │ WEB Solver │ │CRYPTO Solver │
│ (pwntools/ROP│ │(Ghidra/angr) │ │ (SSTI/SQLi/..)│ │(SageMath/Z3) │
└──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
│ │ │ │
└──────────────────┴───────────┬───────────┴──────────────────┘
▼
mcp2agy_workspace/ctf/
├── solves/<challenge>/solve.py (Captured flag: flag{...})
└── writeups/<challenge>.md
1. Category Playbooks & Tooling
1.1 PWN (Binary Exploitation)
- Stack overflows, format string leaks/overwrites, fastbin/tcache heap exploitation, ROP/ret2libc.
- Subagent uses
pwntools,GDB+pwndbg,checksec, andcyclicpatterns.
1.2 REV (Reverse Engineering)
- ELF/PE binary analysis, stripped symbol recovery, anti-debugging defeat, VM opcode decompilation.
- Subagent uses
angr,Ghidra,z3-solver, andcapstone.
1.3 WEB (Web Exploitation)
- SQLi, SSRF, SSTI, Command Injection, Prototype Pollution, JWT confusion, GraphQL batching, Race conditions.
- Subagent uses
requests,playwright,jwt,burp/mitmproxy.
1.4 CRYPTO (Cryptanalysis)
- RSA (small e, Wiener's attack, Hastad broadcast, Common Modulus), AES (ECB Penguin, CBC padding oracle), Discrete Log, Diffie-Hellman, ECC point math.
- Subagent uses
pycryptodome,gmpy2,sympy,z3-solver, SageMath scripts.
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.
- 3d ago First seen · 83 lines · 82 tokens per session scan A 00db994795ab
mcp2agy-ctf is a skill published in the GitHub repository uziii2208/mcp2agy (1 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 1,027 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…