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 agentmods add skills/jonathanung/strike/issue-handlernpx skills add jonathanung/strike --skill issue-handlergit clone --depth 1 https://github.com/jonathanung/strikeWhat 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 | $0.00072 | $0.04009 |
| Opus 5 | $0.00036 | $0.02005 |
| Sonnet 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 yesterday.
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.
- yesterday 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 4d ago), licensed Apache-2.0. It adds 72 tokens to every session and 4,009 once invoked, about $0.0004 per session on Opus 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.