A command that examines the project's milestone, task board, context usage, and setup status to choose the next suggested action. A milestone is a larger piece of planned work made up of tasks.

Use it to continue an active task, start a ready task, create a plan, hand work to a new session, verify completed work, or initialize the project.

It removes the need to manually work out what should happen next when tasks are unfinished, blocked, or not yet planned.

next — Command for Claude Code by benrben/MPGA

Install

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.

Clone the repo

git clone --depth 1 https://github.com/benrben/MPGA

Made for: Claude Code.

Or install mpga, the plugin that ships this one along with the rest of its 18 skills, 26 commands, 3 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/benrben/mpga/next/github.svg)](https://agentmods.dev/commands/benrben/mpga/next)

Your own site

<a href="https://agentmods.dev/commands/benrben/mpga/next"><img src="https://agentmods.dev/badge/commands/benrben/mpga/next/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/benrben/mpga/next"><img src="https://agentmods.dev/badge/commands/benrben/mpga/next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 268 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00000	$0.00268
Opus 5.5	$0.00000	$0.00107
Sonnet 5.5	$0.00000	$0.00054
Haiku 4.5	$0.00000	$0.00027

Measured 2mo ago against content hash fcd7c92ec254, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

mpga-plugin/commands/next.md · 39 lines

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.md for 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

Changes

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.

2mo ago First seen · 39 lines · 0 tokens per session scan A fcd7c92ec254

Subscribe to this mod's changes

next is a command published in the GitHub repository benrben/MPGA (5 stars, last pushed 7mo 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.

Planning Project management

next next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
nextbenrben/MPGA	Command	5	7mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	149k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	149k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	149k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	149k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	149k	today	MIT	A	14	Claude Code
speckit.bug.fixgithub/spec-kit	Command	149k	today	MIT	A	12	Claude Code