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-issuegit 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)<a href="https://agentmods.dev/skills/richkuo/rk-skills/work-on-issue"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/work-on-issue/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"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/work-on-issue.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.00079 | $0.02529 |
| Opus 5 | $0.00039 | $0.01264 |
| Sonnet 5 | $0.00016 | $0.00506 |
| Haiku 4.5 | $0.00008 | $0.00253 |
Grade A, and why
work-on-issue 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 today.
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
Take the issue to a verified, open pull request (PR). The repository's CLAUDE.md/AGENTS.md owns engineering, test-edit, attribution, and Response Style rules. Never pause to ask; report at the end, or stop and report when a gate fails.
Input
An issue number, URL, owner/repo#N, or { issue, targetBranch?, baseRefs?: [{ pr, ref, sha }, ...] }. With no identifier, use the issue validated or planned this session, else stop and ask; never pick one from a list. targetBranch also accepts prose ("target branch develop"). baseRefs pins reviewed predecessor heads in caller order.
Steps
0. Resolve the issue, gate-check it, and detect a plan
Work in a clone whose remotes match the issue's repository; pass -R <owner>/<repo> to every gh command. Read the full body and every comment (gh issue view <N> --comments, paginated) before any mutation.
Gates: the issue is open and no open PR already fixes it. Check gh pr list --state open --search "#<N> in:title,body" and gh issue view <N> --json closedByPullRequestsReferences, then open each candidate; a passing mention does not count, and a PR whose head is this issue's own branch (step 1) routes to step 6. A failed lookup blocks; an existing fix stops the run with its URL.
A plan is a comment starting with ## Implementation plan (any parenthetical model tag), or one a maintainer or caller clearly frames as a plan. Adopt the newest posted plan, even over a caller-supplied one, unless the user selects one; a caller's plan applies only when none is posted. Earlier plans are superseded, never merged. Record its author, source, date, and whether a Fable 5.1 model authored it (heading or footer) for step 6's , fableplan marker. No plan is normal.
1. Create the isolated worktree on a verified base
Target. targetBranch, else gh repo view --json defaultBranchRef -q .defaultBranchRef.name, resolved once and kept through publication. Before shell use, any ref must match ^[A-Za-z0-9][A-Za-z0-9._/@+-]*$, contain no .. or refs/ prefix, and pass git check-ref-format --branch. git ls-remote --heads origin "refs/heads/<target>" must return exactly that ref. git fetch origin <target> and record its commit. A missing or invalid target blocks; never substitute a branch.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed ad1f9919263e
- yesterday Changed · +8 lines · -16 tokens per session 4b80b8d07d9e
- 4d ago Changed 2bc7a0d8410e
- 6d ago Changed · -132 lines · -12 tokens per session 50fbffdca49d
- 10d ago First seen · 195 lines · 107 tokens per session scan A 7a041a690656
work-on-issue is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 2,529 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-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"…
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.
loop-it
An automated workflow that repeatedly fetches open GitHub issues, orders them by dependencies, implements them, reviews the changes, and ships them.
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.