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/benrben/mpga/diagnosenpx skills add benrben/MPGA --skill diagnosegit clone --depth 1 https://github.com/benrben/MPGAWrote 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/benrben/mpga/diagnose)<a href="https://agentmods.dev/skills/benrben/mpga/diagnose"><img src="https://agentmods.dev/badge/skills/benrben/mpga/diagnose.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.00026 | $0.00798 |
| Opus 5 | $0.00013 | $0.00399 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
mpga-diagnose 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
diagnose
Find bugs and quality issues by deploying bug-hunter and optimizer agents in parallel.
Trigger: User wants to find bugs, quality issues, or code problems. Also triggered by: "diagnose this code", "find bugs", "what's wrong with this", "quality check", "code health".
Delegation
Deploy bug-hunter + optimizer agents in parallel:
- bug-hunter agent — checks specifications vs implementation for correctness issues.
- optimizer agent — checks code quality, performance, and maintainability.
Protocol
-
Identify target — determine what to diagnose:
- If user specifies files/directories, use those
- If git diff has changes, diagnose the changed files
- If no target specified, diagnose the current scope or most recently changed files
-
Spawn bug-hunter agent (read-only) to check specifications vs implementation:
- Compare function behavior against documented specifications
- Check edge cases and boundary conditions
- Verify error handling paths
- Look for logic errors, off-by-one, null/undefined risks
- Check type safety and contract violations
- Verify async/await correctness and race conditions
-
Spawn optimizer agent (read-only) in parallel to check code quality:
- Cyclomatic complexity analysis
- Duplicated code detection
- Dead code identification
- Performance anti-patterns (N+1 queries, unnecessary re-renders, etc.)
- Memory leak patterns
- Dependency coupling analysis
-
Collect results from both agents and produce unified diagnosis report:
# DIAGNOSIS REPORT ## Bugs Found (from bug-hunter) | # | File:Line | Severity | Description | Evidence | |---|-----------|----------|-------------|----------| | 1 | ... | CRITICAL | ... | [E] ... | ## Quality Issues (from optimizer) | # | File:Line | Severity | Description | Evidence | |---|-----------|----------|-------------|----------| | 1 | ... | HIGH | ... | [E] ... | ## Priority-Ranked Fix List 1. [CRITICAL] ... — estimated effort: Xh 2. [HIGH] ... — estimated effort: Xh 3. [MEDIUM] ... — estimated effort: Xh ## Summary - Total findings: N - CRITICAL: X | HIGH: Y | MEDIUM: Z | LOW: W - Estimated total effort: Xh
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.
- 5d ago First seen · 92 lines · 26 tokens per session scan A 575ff00a1669
mpga-diagnose is a skill published in the GitHub repository benrben/MPGA (5 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 798 once invoked, about $0.0001 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…