A coding workflow that takes one task from a TODO.md file through planning, implementation, review, and a draft pull request. TDD, or test-driven development, means writing a failing test before the code that makes it pass.

It helps select the next TODO item, agree on the plan, implement it with red-green TDD, open a draft pull request, respond to review comments, and reach a passing CI state.

It breaks a large project plan into one manageable change and keeps the work checked by tests, review discussion, and continuous integration, which is automated code verification.

next-todo — Plugin 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.

Claude Code

/plugin marketplace add kelp/agent-plugins

agentmods

npx agentmods add plugins/kelp/agent-plugins/next-todo

Clone the repo

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

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

next-todo 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/next-todo/.claude-plugin/plugin.json · 11 lines

What it actually says

{
  "name": "next-todo",
  "description": "Land one TODO.md PR slice: choose the next slice, review the plan to consensus, implement with red-green TDD, open a draft pull request, and drain review comments until CI is green.",
  "version": "0.1.0",
  "author": {
    "name": "Travis Cole"
  },
  "homepage": "https://github.com/kelp/agent-plugins",
  "repository": "https://github.com/kelp/agent-plugins"
}

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.

yesterday First seen · 11 lines scan A 5da56bd9ccb5

Subscribe to this mod's changes

next-todo is a plugin published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Code review DevOps and cloud Testing claude claude-code claude-code-plugins llm-training zig zig-lang

next-todo

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

pm-skills

pm-go-to-market

aceternity-ui

handbook-agent-spec-kit

handbook-discover

reflect