Borrowing it
Nothing to install: this file belongs to jonathanung/strike. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonathanung/strike/main/.claude/skills/issue-orchestrator/SKILL.mdgit clone --depth 1 https://github.com/jonathanung/strikeWrote 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/jonathanung/strike/issue-orchestrator)<a href="https://agentmods.dev/skills/jonathanung/strike/issue-orchestrator"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-orchestrator/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/jonathanung/strike/issue-orchestrator"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-orchestrator.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.00071 | $0.01634 |
| Opus 5.5 | $0.00028 | $0.00654 |
| Sonnet 5.5 | $0.00014 | $0.00327 |
| Haiku 4.5 | $0.00007 | $0.00163 |
Grade A, and why
issue-orchestrator 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 2mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue orchestrator (strike-cli)
You coordinate many issues. You do not implement feature code in the primary checkout. Each shippable unit is owned by an issue-handler agent (or you acting as handler for a single issue) inside its own git worktree.
When to use
- User asks to orchestrate / farm / drain open issues
- User wants parallel agents on the backlog
- After filing a wave of issues and wanting them driven to
main
Source of truth
gh issue list --state open --limit 100
gh issue view N
gh pr list --state open
git fetch origin main
git worktree list
Issue body headers (machine-readable)
Issues should start with:
wave: N
depends: none | #a #b
blocks: none | #c #d
conflicts: none | #e #f
priority: bugs-first | feature
| Field | Meaning |
|---|---|
wave |
Lower ships first. Wave 0 = bugs/tests baseline. |
depends |
All listed issues must be CLOSED before start |
conflicts |
Do not run in parallel with these (shared files / same agent) |
blocks |
What this unlocks (scheduling hint) |
priority |
bugs-first before feature within the same wave |
Closed depends count as satisfied.
Missing headers: treat as wave: 99, depends: none, conflicts: none, priority: feature. Prefer issues that have proper headers. When farming, comment once on headerless issues asking for headers (or load issue-create-and-handle to refine) before parallel dispatch — do not guess large parallel graphs.
Suggested conflicts hotspots
Serialize (or mark mutual conflicts) when multiple issues touch:
internal/frontend/tui/app/_src/app/keymap*.go, default keybinds,internal/product/config/keybinds.gointernal/engine/turn.go/ core turn loopinternal/tool/registry.go+ defer/toolsearch wiringinternal/protocolevent kind additions shared across frontends
Prefer explicit conflicts: #N on the issue over silent collision.
Sibling skills
| Skill | Role |
|---|---|
issue-handler |
One issue → worktree → implement → test → PR → review-agent loop → CI → merge → cleanup |
test-and-validate |
Verification report format + tiers |
write-go-tests |
Tests when handler implements |
smoke |
Product happy-path when user-visible |
release |
Version tags (orchestrator does not cut releases unless asked) |
tui-components |
TUI work inside a handler |
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.
- 2mo ago First seen · 158 lines · 71 tokens per session scan A cc8db4d7a2a1
issue-orchestrator is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 1,634 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.
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…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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.
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.
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)…
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…