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 commands/benrben/mpga/nextgit 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.00000 | $0.00268 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
next 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 yesterday.
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
/mpga:next
Auto-detect the next logical action based on current project state. Who can figure out this spaghetti? MPGA alone can fix it.
Decision tree
- Read
MPGA/INDEX.mdfor active milestone - Read board state:
mpga board show --json - Check context budget:
mpga session budget
If context budget is critical (>80% used)
→ Run /mpga:handoff — create handoff and clear context
If blocked tasks exist
→ Show blocked tasks, ask user how to unblock
If in-progress tasks
→ Continue: /mpga:execute <task-id>
If todo tasks ready
→ Pick up the next task whose scope is not already locked by another in-progress write lane: /mpga:execute
If all tasks done
→ Run /mpga:verify, then suggest /mpga:ship
If board is empty and milestone exists
→ Suggest /mpga:plan to generate tasks
If no milestone
→ Suggest mpga milestone new "<name>"
If MPGA not initialized
→ Run /mpga:init — Sad! Get this project started already
Usage
/mpga:next
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.
- yesterday First seen · 39 lines · 0 tokens per session scan A fcd7c92ec254
next is a command published in the GitHub repository benrben/MPGA (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 268 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.