next

next is a command for coding agents from MadAppGang/magus. It costs 48 tokens per session (477 once invoked), scanned A, original, MIT.

A command for showing the next actionable tasks in a Getting Things Done system. Tasks can be filtered by context, energy, estimated time, project, or whether they are waiting on someone else.

In plain words
What is it for?
Use it to find suitable coding, review, or other next actions, such as tasks tagged for a context or those that take no more than a set number of minutes.
Why use it?
It helps you choose work that fits your current situation instead of scanning every task. It also separates actionable work from tasks that are blocked or awaiting a response.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the gtd plugin — 2 skills, 5 commands, 1 agent shipped together

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.

agentmods
npx agentmods add commands/madappgang/magus/next
Clone the repo
git clone --depth 1 https://github.com/MadAppGang/magus

Or install gtd, the plugin that ships this one along with the rest of its 2 skills, 5 commands, 1 agent.

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.

agentmods badge for next

README.md
[![agentmods](https://agentmods.dev/badge/commands/madappgang/magus/next.svg)](https://agentmods.dev/commands/madappgang/magus/next)
Your own site
<a href="https://agentmods.dev/commands/madappgang/magus/next"><img src="https://agentmods.dev/badge/commands/madappgang/magus/next.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 477 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00477
Opus 5 $0.00024 $0.00238
Sonnet 5 $0.00010 $0.00095
Haiku 4.5 $0.00005 $0.00048

Measured yesterday against content hash cbae98e970c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 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.

plugins/gtd/commands/next.md · 45 lines

What it actually says

GTD Next Actions

You are implementing the GTD next command. The user wants to see their actionable next actions, optionally filtered.

Parse the Input

Extract optional filters from the command arguments:

  • --context @tag — filter by context tag (e.g., @code, @review)
  • --energy high|medium|low — filter by energy level
  • --time <minutes> — show only tasks taking <= N minutes
  • --project <name> — filter by project name
  • --waiting — show Waiting For list instead of Next Actions

Display Tasks

Run this Bash command (set filter variables based on parsed arguments):

# Set filter variables from parsed input (replace with actual values or leave empty)
CONTEXT_FILTER=""    # e.g. "@code" or ""
ENERGY_FILTER=""     # e.g. "high" or ""
TIME_FILTER=""       # e.g. "60" or ""
SHOW_WAITING=false   # true if --waiting flag

# Build display command
DISPLAY_ARGS="next"
[ -n "$CONTEXT_FILTER" ] && DISPLAY_ARGS="$DISPLAY_ARGS --context $CONTEXT_FILTER"
[ -n "$ENERGY_FILTER" ] && DISPLAY_ARGS="$DISPLAY_ARGS --energy $ENERGY_FILTER"
[ -n "$TIME_FILTER" ] && DISPLAY_ARGS="$DISPLAY_ARGS --time $TIME_FILTER"
[ "$SHOW_WAITING" = "true" ] && DISPLAY_ARGS="$DISPLAY_ARGS --waiting"

bun run "${CLAUDE_PLUGIN_ROOT}/tools/gtd-display.ts" $DISPLAY_ARGS

After Showing Tasks

  • If tasks were shown: offer "Run /gtd:engage <id> to set an active task, or /gtd:clarify to clarify inbox items."
  • If --waiting was used: mention checking for follow-ups on items waiting > 7 days.
  • If no filters applied and > 10 tasks: suggest using --context @code or --energy high to narrow down.
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.

  1. yesterday First seen · 45 lines · 48 tokens per session scan A cbae98e970c1

Subscribe to this mod's changes

next is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 477 once invoked, about $0.0002 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-09-04.