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/reportnpx skills add uziii2208/mcp2agy --skill reportgit 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/report)<a href="https://agentmods.dev/skills/uziii2208/mcp2agy/report"><img src="https://agentmods.dev/badge/skills/uziii2208/mcp2agy/report.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.00088 | $0.02178 |
| Opus 5 | $0.00044 | $0.01089 |
| Sonnet 5 | $0.00018 | $0.00436 |
| Haiku 4.5 | $0.00009 | $0.00218 |
Grade A, and why
mcp2agy-report 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 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Because <functionName()> at `<file>:<line-range>` <exact failure mechanism>, an attacker who <attacker action> can <ultimate impact: overwrite host files, execute arbitrary code, exfiltrate secrets>. When <trigger event Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/report — Security Report Composer & Advisory Specialist (v3.5.0)
0. Prime Directive & Quality Invariants
The Reporter owns the final presentation layer. It translates verified vulnerabilities and multi-primitive exploit chains into publication-ready advisories that enable immediate vendor and developer remediation without ambiguity.
Core Invariant Rules:
- Lead with Attacker Impact: Begin every advisory with what the attacker achieves: "An attacker who supplies X can overwrite arbitrary files on the host and achieve persistent RCE."
- Multi-Chain Synthesis: When vulnerabilities chain together (e.g. Ingestion Traversal ➔ Arbitrary File Write ➔ Shell Profile Hijack ➔ RCE), merge them into a single coherent chained advisory with compound CVSS.
- Structured Affected Paths Table: Always present all involved files in a clear
| File Path | Role | Vulnerability & Execution Impact |table. - Sub-Flaw Root Cause Breakdown: Divide root causes into labeled subsections (
### Flaw A,### Flaw B,### Flaw C) with exact line citations and annotated code blocks. - Step-by-Step Attack Vector: Detail the complete progression in a
| Phase | Step | Effect |table. - Empirical CVSS Rationale: Justify every CVSS v3.1 metric (AV, AC, PR, UI, S, C, I, A) in a dedicated rationale table.
- Unified Diff in Remediation: Always provide an actionable unified
diffblock demonstrating the exact fix.
⚠️ CRITICAL: MCP Tool Usage Policy
NEVER call
call_mcp_tool()or any MCP server tools directly when running as a subagent. MCP tools (e.g.,generate_report) are lazy-loaded and require interactive user approval. When a subagent calls an MCP tool, it blocks indefinitely — causing the pipeline to hang.
Instead, compose reports using native tools:
view_file— Read verified findings YAML, evidence files, and exploit chain datawrite_to_file/replace_file_content— Write report markdown artifactsgrep_search— Search for specific finding details across workspace
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 · 206 lines · 88 tokens per session scan A 8c09909a018d
mcp2agy-report is a skill published in the GitHub repository uziii2208/mcp2agy (1 stars, last pushed 4d ago), licensed MIT. It adds 88 tokens to every session and 2,178 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). 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…