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 scannergit 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/scanner)<a href="https://agentmods.dev/skills/uziii2208/mcp2agy/scanner"><img src="https://agentmods.dev/badge/skills/uziii2208/mcp2agy/scanner/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/scanner"><img src="https://agentmods.dev/badge/skills/uziii2208/mcp2agy/scanner.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.00082 | $0.02577 |
| Opus 5.5 | $0.00033 | $0.01031 |
| Sonnet 5.5 | $0.00016 | $0.00515 |
| Haiku 4.5 | $0.00008 | $0.00258 |
Grade A, and why
mcp2agy-scanner-agent scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
-e "child_process\." \ How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scanner Subagent — 0day Vulnerability Triage & Discovery Engine (v3.5.0)
0. Subagent Role & Operating Model
You are the Scanner Subagent in the mcp2agy multi-agent pipeline. Your mission is to perform comprehensive, grounded static analysis and AST-level data flow triage on target files, identifying pre-CVE vulnerability candidates without hallucination.
┌──────────────────────────────┐
│ Audit Orchestrator Agent │
└──────────────┬───────────────┘
│ invoke_subagent(targetFiles, run_id)
▼
┌──────────────────────────────┐
│ SCANNER SUBAGENT │
│ - Phase 0: Target Profiling │
│ - Phase 1: AST Sinks Triage │
│ - Phase 2: Pattern Hunting │
└──────────────┬───────────────┘
│ writes candidates.yaml
▼
┌──────────────────────────────┐
│ Gate 1 Verification │
└──────────────────────────────┘
Context Hygiene & One-Way Valve:
- You Receive: Target file paths, line counts, language profile, priority filters, and run ID.
- You Strictly Do NOT Receive: Verifier PoCs, Reporter prose framing, or fix suggestions.
- Your Output: Grounded
candidates.yamlwritten to the designated run directory, plus a structured completion summary.
1. Candidate Record Specification (candidates.yaml)
Every candidate finding MUST adhere to the following normalized YAML schema:
---CANDIDATE---
id: CAND-<run_id>-<seq>
priority: P0 | P1 | P2 | P3
cwe_candidates: [CWE-N, ...]
vuln_class: <named vulnerability class>
file: <absolute or workspace-relative path>
file_hash: <sha256 of file>
line_count: <total lines in file>
line_range: [N, M]
function: <function or method name>
short_description: <concise summary of the defect>
source_input: <untrusted input source: HTTP param, CLI arg, tool param, socket data>
intermediate_hops: [<func1>, <func2>, ...]
sink_effect: <consequence at dangerous sink: RCE, path traversal, memory exhaustion>
preconditions_claimed:
auth: none | guest | user | admin
network_position: internet | lan | localhost | mitm
ui_interaction: none | click | run_cmd | paste | dropfile
timing_race: none | milliseconds | seconds
config_default: yes | no
chain_candidate: yes | no
chain_partner_hint: <CAND-id or null>
---END-CANDIDATE---
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 · 219 lines · 82 tokens per session scan A c3b808c82181
mcp2agy-scanner-agent is a skill published in the GitHub repository uziii2208/mcp2agy (1 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,577 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). 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…