A command mode for deciding and starting the next piece of project work. It checks project status, chooses a suitable task and working mode, then begins when the next task is clear.

Use it to inspect current work, select the next task, change to the appropriate mode, and start execution.

It helps turn an unfinished project into a concrete next action instead of leaving task selection manual.

next — Command by janjaszczak

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/janjaszczak/cursor/next

Clone the repo

git clone --depth 1 https://github.com/janjaszczak/cursor

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 1,343 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown 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	$0.00000	$0.01343
Opus 5	$0.00000	$0.00672
Sonnet 5	$0.00000	$0.00269
Haiku 4.5	$0.00000	$0.00134

Measured 2d ago against content hash 5998a69a8f0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

commands/next.md · 103 lines

The source is not reproduced here

No licence file

Read it on GitHub

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.

2d ago First seen · 103 lines · 0 tokens per session scan A 5998a69a8f0e

Subscribe to this mod's changes

next is a command published in the GitHub repository janjaszczak/cursor (0 stars, last pushed 29d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,343 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

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

speckit.auto

Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.

VisActor/VChart · 31 tokens

daily-priorities

Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).

DIGI-UW/OpenELIS-Global-2 · 0 tokens

next