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 skills add uziii2208/mcp2agy --skill exploitgit 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/exploit)<a href="https://agentmods.dev/skills/uziii2208/mcp2agy/exploit"><img src="https://agentmods.dev/badge/skills/uziii2208/mcp2agy/exploit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/uziii2208/mcp2agy/exploit"><img src="https://agentmods.dev/badge/skills/uziii2208/mcp2agy/exploit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00087 | $0.01024 |
| Opus 5.5 | $0.00035 | $0.00410 |
| Sonnet 5.5 | $0.00017 | $0.00205 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
mcp2agy-exploit 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 2mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/exploit — Exploit Development & Weaponization Engine (v3.0.0)
0. Prime Directive & Operating Model
The Exploit engine turns verified vulnerabilities and security primitives into working, deterministic exploit scripts:
┌───────────────────────────────────┐
│ Exploit Orchestrator (/exploit) │
└─────────────────┬─────────────────┘
│
┌───────────────────┬───────────┴───────────┬───────────────────┐
▼ ▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ Memory Corrupt│ │ Web & API Bug │ │ Logic & Auth │ │ Exploit Chain │
│ (pwntools/ROP)│ │ (SSRF/SSTI/..)│ │ (Race/PrivEsc)│ │ Assembler │
└───────────────┘ └───────────────┘ └───────────────┘ └───────────────┘
│ │ │ │
└───────────────────┴───────────┬───────────┴───────────────────┘
▼
mcp2agy_workspace/exploits/
├── pocs/<target>_<cwe>.py
├── payloads/
└── chains/<chain_id>_full_rce.py
1. Exploit Categories & Tooling
1.1 Memory Corruption Exploitation
- Stack & Heap Exploits: Buffer overflows, heap chunk consolidation, fastbin/tcache poisoning, Use-After-Free (UAF).
- Modern Mitigations: ASLR defeat via info leak, DEP/NX bypass via ROP/JOP gadget chains, Stack Canary bypass.
- Tools:
pwntools,angr,z3-solver, GDB withpwndbg/gef.
1.2 Web & Application Layer Exploits
- Command & Code Injection: Shell escape breakout, argument injection, double-quoted context differentials (
_pde). - Server-Side Template Injection (SSTI): Jinja2, Mako, FreeMarker, Pug, Handlebars sandboxed environment escapes.
- SSRF to Cloud Metadata: AWS IMDSv1/v2, GCP metadata headers, internal Kubernetes service tokens.
- Insecure Deserialization: Java
ysoserialchains (CommonsCollections, Spring), Pythonpickle/yamlgadgets, PHP object injection.
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.
- 2mo ago First seen · 84 lines · 87 tokens per session scan A cbfbe38eae82
mcp2agy-exploit is a skill published in the GitHub repository uziii2208/mcp2agy (1 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 1,024 once invoked, about $0.0003 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…