What is next-todo-init?

A setup command that adds a Next TODO configuration section to a project's CLAUDE.md file. CLAUDE.md is a project instruction file read by Claude Code.

Use it when starting a project with the Next TODO workflow. Afterward, fill in the backlog, planning, specification, checks, continuous integration, review, and rules settings.

It avoids manually creating the configuration and prevents adding it twice when the binding already exists.

next-todo-init — Skill by kelp

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 skills/kelp/agent-plugins/next-todo-init

Any agent

npx skills add kelp/agent-plugins --skill next-todo-init

Clone the repo

git clone --depth 1 https://github.com/kelp/agent-plugins

Made for: Claude Code, Codex.

Or install next-todo, the plugin that ships this one along with the rest of its 2 skills.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 320 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.

Model	Per session	Once invoked
Fable 5	$0.00032	$0.00320
Opus 5	$0.00016	$0.00160
Sonnet 5	$0.00006	$0.00064
Haiku 4.5	$0.00003	$0.00032

Measured 2d ago against content hash 8caedcf68f59, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

next-todo-init 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.

plugins/next-todo/skills/next-todo-init/SKILL.md · 45 lines

What it actually says

/next-todo-init

Add Next TODO binding to this project's CLAUDE.md.

Procedure

1. Read the configuration fragment

Read the file at ${CLAUDE_PLUGIN_ROOT}/docs/claude-md-fragment.md. This contains the Next TODO binding template formatted as a CLAUDE.md section.

2. Check current CLAUDE.md

If no CLAUDE.md exists in the project root, create one with just a # CLAUDE.md header followed by the fragment content.
If CLAUDE.md exists, check if it already contains "Next TODO binding". If so, report "Next TODO binding already present" and stop.
If CLAUDE.md exists but lacks the binding, append the fragment content to the end of the file.

3. Report result

Tell the user what you did:

"Created CLAUDE.md with Next TODO binding"
"Added Next TODO binding to existing CLAUDE.md"
"Next TODO binding already present in CLAUDE.md"

4. Next steps

Tell the user to fill in the seven binding values: backlog, plan, spec, gates, CI, review axes, and rules.

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 · 45 lines · 32 tokens per session scan A 8caedcf68f59

Subscribe to this mod's changes

next-todo-init is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 10d ago), licensed MIT. It adds 32 tokens to every session and 320 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-08-31.

claude claude-code claude-code-plugins llm-training zig zig-lang

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy…

phuryn/pm-skills · 78 tokens

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

phuryn/pm-skills · 52 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

competitive-battlecard

Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.