A command that examines local planning files and, when available, broader company planning files to identify the next work, blockers, and a recommended action. It uses handoff notes, status files, and state records.

Use it to decide what to work on next, understand why an item is waiting, and see what is blocking it. It can include goals from the repository and related planning areas.

It turns scattered planning information into a focused next-step briefing. If the repository is not connected to a larger planning system, it falls back to local information.

How bredmond1019/claude-sdk-rs configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bredmond1019/claude-sdk-rs/main/.claude/commands/next.md

Clone the repo

git clone --depth 1 https://github.com/bredmond1019/claude-sdk-rs

Made for: Claude Code.

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/bredmond1019/claude-sdk-rs/next/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/next)

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/next"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/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/bredmond1019/claude-sdk-rs/next"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 814 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.00025	$0.00814
Opus 5.5	$0.00010	$0.00326
Sonnet 5.5	$0.00005	$0.00163
Haiku 4.5	$0.00003	$0.00081

Measured 11d ago against content hash 3ad5b77bb22f, 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 11d 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.

.claude/commands/next.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Next — What's up next, what's blocked, and recommendation

Show what's next, why, what's blocked and by what, and recommend the next action based on local context (like handoff.md, status.md, and state.json) and overall company goals in HQ, Business, and Core.

Instructions

Locate Brain Root (BRAIN_ROOT): Walk up from the current directory looking for brain.toml.
- If not found, run as a standalone repository (degrade gracefully: skip HQ, Business, and Core goals sections and base the recommendation solely on local files).
- If found, mark that directory as BRAIN_ROOT.
Read Local planning files:
- Check if planning/handoff.md exists. If so, read it.
- Read planning/status.md (current focus and momentum).
- Read planning/state.json (focus and carryover array).
Read Brain / Sibling goals (if brain.toml is found):
- Read planning/status.md in BRAIN_ROOT (HQ Company Brain goals and Operating Board).
- Read business/planning/status.md in BRAIN_ROOT (Business sub-brain goals).
- Read core/planning/status.md in BRAIN_ROOT (Core sub-brain goals).
Synthesize the State:
- Up Next: Identify items that are ready to be worked on. This includes:
  - The first command and remaining tasks in planning/handoff.md (if present).
  - Focus "now" or "next" items in local planning/status.md or planning/state.json.
  - Carryover items in local planning/state.json that are active.
- Blocked: Identify items that are blocked, what they are blocked by, and why (from local planning/status.md or planning/state.json).
- HQ/Business/Core context: Summarize the active company/sub-brain focus in 1-2 sentences each.
Generate the Recommendation:
- Recommend a single next command/action.
- Provide a clear, logical explanation for why this is recommended, showing how it unblocks local carryovers or tasks, and how it aligns with the overall goals of HQ, Business, or Core.
- If there are multiple items that could be next, briefly present each option (with a one-sentence overview) and justify why the recommended one is preferred.

Read the full file on GitHub · 67 lines

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.

11d ago First seen · 67 lines · 25 tokens per session scan A 3ad5b77bb22f

Subscribe to this mod's changes

next is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 814 once invoked, about $0.0001 per session on Opus 5.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-10-26.

Planning Project management

next next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
nextbredmond1019/claude-sdk-rs	Command	23	1mo ago	Apache-2.0	A	25	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-sdk-rs: Command for Claude Code