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/asknpx skills add benrben/MPGA --skill askgit clone --depth 1 https://github.com/benrben/MPGAWhat 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.00028 | $0.01153 |
| Opus 5 | $0.00014 | $0.00576 |
| Sonnet 5 | $0.00006 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
mpga-ask 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ask
Evidence-backed answers. Evidence First — always.
Trigger: User asks "how does X work?", "where is X?", "what does X do?".
The Winning Protocol
- Read
MPGA/INDEX.mdfor scope registry — find the SMALLEST relevant scopes first. Precision, people. We don't do sloppy. - Read relevant scope document(s) — the answers are in there.
- Answer the question using evidence links as citations — evidence, not guessing.
- If the answer is incomplete — and sometimes, very rarely, it happens:
- Spawn one read-only
scoutper missing scope in PARALLEL. - Ask each scout for evidence, traces, and unknowns only for its assigned scope.
- Merge the findings into one answer.
- Spawn one read-only
- If the answer is already in scope docs, do NOT rescan the whole codebase.
- NEVER modify any files — read-only.
Confidence Scoring — We Rate EVERYTHING, Total Transparency
Rate EVERY claim in the answer with a confidence level — because we don't hide, we don't hedge, we SCORE:
- HIGH — Directly verified in source code or scope docs. You read the file, you saw the line, it's RIGHT THERE.
- Format:
[HIGH] <claim> — [E] path/to/file.ts:42 :: functionName()
- Format:
- MEDIUM — Inferred from patterns, naming conventions, or related code. Reasonable but not directly confirmed.
- Format:
[MEDIUM] <claim> — inferred from [E] path/to/file.ts:42 :: similar pattern
- Format:
- LOW — Educated guess based on general knowledge or incomplete evidence. Could be WRONG.
- Format:
[LOW] <claim> — no direct evidence found, based on <reasoning>
- Format:
If the overall answer confidence is LOW, say so upfront: "This answer has LOW confidence — consider verifying with a scout or reading the code directly."
Source Citations — Show Your Receipts, Always
Every claim MUST cite the specific source — no citations, no credibility. It's very simple:
- For code:
[E] src/module/file.ts:42-67 :: functionName() — <what it does> - For scope docs:
[E] MPGA/scopes/<scope>.md — <what it says> - For config files:
[E] path/to/config.json:key.path — <what it configures> - If no source exists:
[Unknown] <claim> — not documented, needs investigation
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.
- 2d ago First seen · 107 lines · 28 tokens per session scan A 9ce5f77e689c
mpga-ask is a skill published in the GitHub repository benrben/MPGA (5 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 1,153 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.
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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…