Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kelp/agent-plugins/plugin install next-issueWrote 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.
[](https://agentmods.dev/skills/kelp/agent-plugins/next-issue-init)<a href="https://agentmods.dev/skills/kelp/agent-plugins/next-issue-init"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/next-issue-init/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.
<a href="https://agentmods.dev/skills/kelp/agent-plugins/next-issue-init"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/next-issue-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00032 | $0.00391 |
| Opus 5.5 | $0.00013 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
next-issue-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 1mo 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.
What it actually says
/next-issue-init
Add Next issue 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 issue binding template formatted
as a CLAUDE.md section.
2. Check current CLAUDE.md
- If no
CLAUDE.mdexists in the project root, create one with just a# CLAUDE.mdheader followed by the fragment content. - If
CLAUDE.mdexists, check if it already contains "Next issue binding" or the old heading "Next TODO binding". If so, report that the binding is already present and stop. Do not add a second copy. - If
CLAUDE.mdexists but lacks both headings, append the fragment content to the end of the file.
3. Report result
Tell the user what you did:
- "Created CLAUDE.md with Next issue binding"
- "Added Next issue binding to existing CLAUDE.md"
- "Issue binding already present in CLAUDE.md"
4. Next steps
Tell the user to fill in the eight binding values:
backlog, plan, spec, gates, CI, review axes, rules, and
claims (optional).
The backlog is a GitHub repository. Tell the user to
create the labels parent, ready, in-progress, and
blocked in that repository when they do not exist.
Previously this command was /next-todo-init.
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.
- 1mo ago First seen · 52 lines · 32 tokens per session scan A d3724da068e4
next-issue-init is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 391 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-09-07.
Other skills, from other repositories
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.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
review-resume
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
identify-assumptions-new
Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.
wwas
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
brainstorm-ideas-existing
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.