A GitHub issue orchestrator that handles all remaining child issues under one parent issue. GitHub Issues are task records, and each child issue is treated as work that should become a pull request, a proposed code change for review.

Use it to select a parent issue and run the issue workflow once for each open child issue.

It removes the need to start the child-issue workflow manually for every task. It also keeps the work tied to the project's documented rules and live GitHub queue.

next-parent — Skill for Claude Code by kelp/agent-plugins

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.

Any agent

npx skills add kelp/agent-plugins --skill next-parent

Clone the repo

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

Made for: Claude Code.

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

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/skills/kelp/agent-plugins/next-parent/github.svg)](https://agentmods.dev/skills/kelp/agent-plugins/next-parent)

Your own site

<a href="https://agentmods.dev/skills/kelp/agent-plugins/next-parent"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/next-parent/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/skills/kelp/agent-plugins/next-parent"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/next-parent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,160 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.00070	$0.02160
Opus 5.5	$0.00028	$0.00864
Sonnet 5.5	$0.00014	$0.00432
Haiku 4.5	$0.00007	$0.00216

Measured 1mo ago against content hash c3034b76f452, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

next-parent 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.

plugins/next-issue/skills/next-parent/SKILL.md · 211 lines

How it starts

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

/next-parent

Orchestrator only. It does not replace /next-issue. That skill still lands one sub-issue. This skill picks one parent GitHub issue, then runs /next-issue once per remaining open sub-issue.

The live queue is GitHub Issues. A parent issue is a category. Each sub-issue is one PR. TODO.md is an archive, not the picker.

The project's CLAUDE.md is the architecture contract. If this skill conflicts with that file or the Rules binding, follow those files.

Input

Parent: $ARGUMENTS

Empty → the parent of the next ready or in-progress sub-issue (§1).
A parent issue number, or a unique title substring → that parent.

Binding

Same eight values as /next-issue. Read ## Next issue binding in the project's CLAUDE.md. If that heading is missing, read ## Next TODO binding. If both are missing, stop and tell the user to run /next-issue-init.

This skill uses Backlog, Plan, CI, Rules, and Claims. Plan, TDD, and patch review stay in /next-issue.

Overlay (every next-issue run)

Pass these into each /next-issue invocation. They override that skill's "one slice then stop" and "branch from origin/main" steps for this session only:

GitHub PR base is main. Never a feature branch.
The first sub-issue branches from origin/main. Each later sub-issue branches from the previous slice HEAD. Later branches may contain earlier slice commits. That is a commit stack, not a stacked-PR base.
Do not open a second PR for a sub-issue that already has an open PR against main.
In the PR body, name predecessor PRs in this stack and the slice-only range as two SHAs (<prev-tip>..<slice-tip>), not a symbolic HEAD. The first push creates the branch before the draft PR exists; write the range into the body when the PR opens. Update that range before every later push of the slice, including a patch-review or drain fix pushed by next-issue. The PR body is the recovery record. Stop and report if an open PR has no range.
Patch review (next-issue §4b) reviews the slice-only range <prev-tip>..HEAD against this slice's plan, not origin/main...HEAD. Gates still run on the whole branch. The same range applies when a drain fix triggers patch review again.
Do not merge. Do not enqueue on the merge queue unless the user asks.

Read the full file on GitHub · 211 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.

1mo ago First seen · 211 lines · 70 tokens per session scan A c3034b76f452

Subscribe to this mod's changes

next-parent is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 2,160 once invoked, about $0.0003 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.

Claude Code Git and workflow Project management claude claude-code-plugins llm-training zig zig-lang

glab

Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.

NikiforovAll/claude-code-rules · 59 tokens

next-parent

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/next-parent

Input

Binding

Overlay (every next-issue run)

What this file has done since we first saw it

Other skills, from other repositories

glab

github-backlog-triage

git-history-analysis

feature-flow

create-issue

atomic-issues-prs