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-handler/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-handler)<a href="https://agentmods.dev/skills/jonathanung/strike/issue-handler"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-handler/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-handler"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-handler.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.00072 | $0.04009 |
| Opus 5.5 | $0.00029 | $0.01604 |
| Sonnet 5.5 | $0.00014 | $0.00802 |
| Haiku 4.5 | $0.00007 | $0.00401 |
Grade A, and why
issue-handler 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue handler (strike-cli)
Own the issue end-to-end with due diligence on research, testing, and validation. Shipping is ownership: commit → push → PR → review-agent loop → CI green → merge → cleanup. All code edits happen inside a git worktree, never the primary checkout.
For agents developing strike. Authoring skills/docs may use this pipeline; apply when the user frames work as an issue (or asks you to own issue→main).
Preconditions
gh auth statusok; git repo; network; issue number/URL known.- Stop-and-ask: no write access;
ghmissing; issue already has an open PR you did not create (attach or ask — no duplicate). Dirty primary is fine forgit worktree addfromorigin/main— do not clean/stash primary WIP.
Workflow
- Orient —
gh issue view N(+ comments). ReadAGENTS.md+docs/ARCHITECTURE.mdfor boundaries. Note issue headers (wave/depends/conflicts/priority) if present. - Research — map issue→packages; read code + nearest tests. Optional local
.plan/features.md/FEATURES_STATUS.mdif present (never block if missing). State acceptance criteria bullets. Stop-and-ask if ambiguous. - Worktree — create/enter; confirm
pwd+ branch before edits. - Plan — smallest correct change; no drive-by refactors. Assign risk tier A/B/C (see Verification tiers).
- Implement — worktree only; load sibling skills when domain matches.
- Test — load
write-go-testswhen behavior changes. - Validate — load
test-and-validatefor the tier gate; smoke when applicable. - Sync main — if the PR will be open >~1h or
origin/mainmoved,git fetch origin main && git merge origin/mainthen re-run tier gate before/at push. - Ship — commit, push
origin/<branch>, PR withFixes #N. - Review loop — tier-scaled (below); post findings; address; re-review until merge-ready.
- Babysit CI — fix branch-related failures; re-push; re-enter review loop after material code changes.
- Merge — only when merge gates pass (below).
- Cleanup — remove worktree after merge; leave cwd outside deleted tree.
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 · 311 lines · 72 tokens per session scan A 2646888fbd1f
issue-handler is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 4,009 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…