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.
npx skills add kelp/agent-plugins --skill next-issuegit clone --depth 1 https://github.com/kelp/agent-pluginsWrote 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)<a href="https://agentmods.dev/skills/kelp/agent-plugins/next-issue"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/next-issue/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"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/next-issue.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.00105 | $0.04291 |
| Opus 5.5 | $0.00042 | $0.01716 |
| Sonnet 5.5 | $0.00021 | $0.00858 |
| Haiku 4.5 | $0.00011 | $0.00429 |
Grade A, and why
next-issue 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.
How it starts
The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next-issue
Do this whole procedure for one slice. Do not skip the plan review. Do not skip the comment drain. Do not start a second slice in the same change.
The project's CLAUDE.md is the architecture contract. This skill is the operating procedure. If this skill conflicts with that file or the Rules binding, follow those files.
Input
Slice: $ARGUMENTS
- Empty → pick the next child issue from the backlog (§1).
- An issue number → that child issue is the slice. Do not ask the user
which issue to take. An orchestrator such as
/next-parentpasses this number once per child.
Binding
Read ## Next issue binding in the project's CLAUDE.md. If
that heading is missing, read ## Next TODO binding (the
old name). If both are missing, stop and tell the user to
run /next-issue-init first.
Every value marked (binding) below comes from that section:
- Backlog — the GitHub repository that holds the issues.
- Plan — where the plan artifact lives. A local Plan there may refine child order for one session.
- Spec — spec file(s) and the approval rule.
- Gates — local commands before each commit.
- CI — required checks the parent waits on.
- Review axes — replacements for the defaults below, if any.
- Rules — TDD, style, and dependency files.
- Claims — optional. A command that takes one issue number, takes
a lock on that issue, and prints the directory to work in. Unset
means no lock: branch from
mainin the current checkout.
When to use
Use this skill when the user asks to land a slice, do the next child issue, plan a slice, or drain PR review comments to all-clear.
Do not use this skill for work that is not a child issue, unless the user maps that work onto a named child issue. Do the user's requested work instead.
1. Choose the work
The live work queue is GitHub Issues in the repository that Backlog (binding) names. The labels are the state:
parentmarks a category issue. A parent issue is not work.- A child issue is a sub-issue of a parent. One child issue is one pull request.
- A child issue carries
ready,in-progress, orblocked.
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 · 418 lines · 105 tokens per session scan A 39e7ef8efb63
next-issue is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 4,291 once invoked, about $0.0004 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
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
product
Consolidated Galyarder Framework Product intelligence bundle.
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
create-issues
Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.