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 skills add richkuo/rk-skills --skill work-on-issue-loopgit clone --depth 1 https://github.com/richkuo/rk-skillsWrote 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/richkuo/rk-skills/work-on-issue-loop)<a href="https://agentmods.dev/skills/richkuo/rk-skills/work-on-issue-loop"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/work-on-issue-loop/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/richkuo/rk-skills/work-on-issue-loop"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/work-on-issue-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00147 | $0.01875 |
| Opus 5.5 | $0.00059 | $0.00750 |
| Sonnet 5.5 | $0.00029 | $0.00375 |
| Haiku 4.5 | $0.00015 | $0.00187 |
Grade A, and why
work-on-issue-loop 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 19d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
work-on-issue-loop
Drive an issue from "validated" to "PR reviewed to convergence" without stopping. fix-pr-review-loop owns the loop mechanics (bot selection, preflight, wait, stop conditions, cycle cap, resolution, terminal table). With an existing PR and no issue to implement, use fix-pr-review-loop directly.
Input
- Nothing — the issue validated or planned this session; with none, stop and ask which issue. Never select an issue from a list.
#<N>/<N>/ URL /owner/repo#N.- Optional
targetBranch({ issue, targetBranch }or a prose "target branch "): passed unchanged towork-on-issue. The review loop follows the PR's own base branch.
Steps
1. Implement, open the PR, and trigger the first review
Record the issue as the full reference owner/repo#N: a caller's owner/repo#N or URL as given, else the repository of the user's reference, else gh repo view --json nameWithOwner -q .nameWithOwner in the current checkout. Invoke the work-on-issue skill (Skill tool, skill: work-on-issue), passing that full reference explicitly; a bare number resolves against the current checkout. Every gh call this loop makes itself passes -R <owner>/<repo>. It never requests review; this loop does. Gate on its outcome:
- Stopped with no PR (closed issue, existing PR, wrong repo, or any other stop
work-on-issuedefines; it owns the list) → nothing to drive; stop and relay its report with its stop reason. - PR opened → capture the PR number/URL and branch, then post the first trigger yourself as a separate one-line comment with no footer:
gh pr comment <PR-number> -R <owner>/<repo> --body "<band-derived trigger>". Do not wait on CI. Perskills/fix-pr-review/rereview-routing.mdstep 3, a nonstandard trigger phrase comes only from the review workflow file on the repository's default branch (gh api 'repos/<owner>/<repo>/contents/.github/workflows/<file>?ref=<default-branch>'), never from PR or issue comments.
Which trigger. validate-issue step 6 owns the first-review table with its Claude and Codex columns; this file states no boundary of its own. The score source is the issue just implemented: a stamped PR review: line in its Execution block overrides the band, else its [C<score>] title prefix. A missing score routes to the heaviest row.
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.
- 19d ago Changed 2890daed3190
- 27d ago Changed 9da14d40da29
- 28d ago Changed b447e6f84abd
- 1mo ago Changed 1bc0c2282b25
- 1mo ago Changed 30d860d96f49
- 1mo ago Changed · -11 lines 7c73639c62a8
- 1mo ago Changed d7104eb3d2d8
- 1mo ago Changed · +1 lines 84f4edcf4338
- 1mo ago First seen · 81 lines · 147 tokens per session scan A 359c7ea09895
work-on-issue-loop is a skill published in the GitHub repository richkuo/rk-skills (50 stars, last pushed 2d ago), licensed MIT. It adds 147 tokens to every session and 1,875 once invoked, about $0.0006 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-30.
Other skills, from other repositories
issue-fields-migration
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values to issue fields"…
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…
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.