agentmods.dev

orchestrate-tickets

orchestrate-tickets is a skill for Claude Code from johardi/claude-stack. It costs 66 tokens per session (2,123 once invoked), scanned A, original, MIT.

A workflow for splitting a parent GitHub issue into dependent sub-tickets and handling them as separate pull requests. GitHub issues track work, while pull requests propose code changes for review.

In plain words
What is it for?
Running multiple sub-tickets, creating one pull request per ticket, and coordinating their dependencies.
Why use it?
It coordinates related tasks across isolated git worktrees, reducing conflicts between parallel changes and leaving a human merge decision between waves.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cstack-collab plugin — 5 skills, 3 hooks shipped together

not rated 2repo 5mo ago A scan 66 tokens original MIT

Good fit Running multiple sub-tickets, creating one pull request per ticket, and coordinating their dependencies.

Compare 6 skills from other repositories ↓
View source ↗ johardi/claude-stack
Install

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.

Claude Code
/plugin marketplace add johardi/claude-stack
Claude Code
/plugin install cstack-collab

Made for: Claude Code.

Or install cstack-collab, the plugin that ships this one along with the rest of its 5 skills, 3 hooks.

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.

agentmods badge for orchestrate-tickets

README.md
[![agentmods](https://agentmods.dev/badge/skills/johardi/claude-stack/orchestrate-tickets/github.svg)](https://agentmods.dev/skills/johardi/claude-stack/orchestrate-tickets)
Your own site
<a href="https://agentmods.dev/skills/johardi/claude-stack/orchestrate-tickets"><img src="https://agentmods.dev/badge/skills/johardi/claude-stack/orchestrate-tickets/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.

agentmods 80×15 button for orchestrate-tickets

Your own site · 80×15
<a href="https://agentmods.dev/skills/johardi/claude-stack/orchestrate-tickets"><img src="https://agentmods.dev/badge/skills/johardi/claude-stack/orchestrate-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,123 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.02123
Opus 5.5 $0.00026 $0.00849
Sonnet 5.5 $0.00013 $0.00425
Haiku 4.5 $0.00007 $0.00212

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

Security

Grade A, and why

orchestrate-tickets 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/cstack-collab/skills/orchestrate-tickets/SKILL.md · 131 lines

How it starts

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

Orchestrate Tickets

Multi-agent orchestration of a parent GitHub issue plus dependent sub-tickets. One PR per sub-ticket, with a human-in-the-loop merge gate between waves.

When to Use

Use when:

  • The user references a parent issue with sub-tickets (a checklist of #N items in the parent body).
  • The user explicitly lists multiple issue numbers and asks for them to be coordinated.
  • The user says: "orchestrate", "coordinate", "fan out", "run the sub-tickets", "open separate PRs for these".

Skip when:

  • It is a single issue with no children → use the github-issue-workflow skill instead.
  • The user wants a single PR that covers everything → use github-issue-workflow against the parent.

How This Skill Stays Deterministic

Most of the work below is delegated to scripts and hooks that ship with this plugin. Treat their exit codes and stdout as the source of truth — do not paraphrase issue bodies, do not re-derive PR merge state from gh text output, do not hand-edit issue bodies. Specifically:

Step Tool
Preflight (gh, git, clean tree, default branch) ${CLAUDE_PLUGIN_ROOT}/scripts/check-prereqs.sh
Build the dependency DAG ${CLAUDE_PLUGIN_ROOT}/scripts/build-dag.py
Initialize / read / mutate state ${CLAUDE_PLUGIN_ROOT}/scripts/state.py
Render the worker prompt ${CLAUDE_PLUGIN_ROOT}/scripts/worker-prompt.sh
Check whether a wave's PRs are merged ${CLAUDE_PLUGIN_ROOT}/scripts/wave-status.py
Update the parent issue's checklist ${CLAUDE_PLUGIN_ROOT}/scripts/update-parent-checklist.py

Hooks bundled with this plugin enforce the trickier invariants regardless of model behavior:

  • PreToolUse(Bash) denies gh pr merge against any child PR while orchestration is active.
  • PreToolUse(Bash) denies gh issue close <PARENT> while children are unmerged, and denies gh issue edit <PARENT> --body unless the body carries the <!-- cstack-collab:checklist --> marker emitted by update-parent-checklist.py.
  • PostToolUse(Agent) records the worker's PR result in state.json automatically when the subagent is named ticket-N.
  • SessionStart prints a one-line summary if an orchestration is in progress in the current repo.

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

  1. 1mo ago First seen · 131 lines · 66 tokens per session scan A c3defab3c446

Subscribe to this mod's changes

orchestrate-tickets is a skill published in the GitHub repository johardi/claude-stack (2 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 2,123 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-08-31.

Git and workflowProject management
Related

Other skills, from other repositories

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens