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/onboardnpx skills add benrben/MPGA --skill onboardgit 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/onboard)<a href="https://agentmods.dev/skills/benrben/mpga/onboard"><img src="https://agentmods.dev/badge/skills/benrben/mpga/onboard.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.00014 | $0.00307 |
| Opus 5 | $0.00007 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
mpga-onboard 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 4d 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.
What it actually says
onboard
Trigger: User is new to the codebase or starting a fresh session.
Protocol
- Read
MPGA/INDEX.md— present the project identity section. - Explain the project type, size, and key languages — the big picture.
- Walk through the scope registry:
- For each scope: what it does, key files, primary responsibilities.
- Highlight the dependency graph from GRAPH.md — how everything connects.
- Show active milestone and current board state — what we're building right now.
- Identify the most relevant scope(s) for the user's likely work.
- Suggest: "Which area would you like to explore first? We have well-documented code in every direction."
Presentation order
- Project identity
- Architecture overview
- Key entry points
- Active work
- Suggested starting points
Voice announcement
If spoke is available (mpga spoke --help exits 0), announce completion:
mpga spoke '<brief 1-sentence result summary>'
Keep the message under 280 characters.
Strict rules
- Do NOT overwhelm with all information at once — present in sections.
- Ask which area the user wants to dig into after the overview.
- Cite evidence links for all claims about the codebase.
- If scope docs are stale → mention it and suggest
mpga sync.
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.
- 4d ago First seen · 43 lines · 14 tokens per session scan A 5085b3b130f8
mpga-onboard is a skill published in the GitHub repository benrben/MPGA (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 307 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…