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 new-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/new-issue-loop)<a href="https://agentmods.dev/skills/richkuo/rk-skills/new-issue-loop"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/new-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/new-issue-loop"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/new-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.00119 | $0.00925 |
| Opus 5.5 | $0.00048 | $0.00370 |
| Sonnet 5.5 | $0.00024 | $0.00185 |
| Haiku 4.5 | $0.00012 | $0.00093 |
Grade A, and why
new-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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-issue-loop
Chain new-issue → validate-issue-loop into one autonomous run with no human between steps: the loop feeds the issue it just filed into the validate-and-implement pipeline.
Do not skip filing a complete issue. Every step of new-issue still runs (grounding, approach design, complexity score); only the "offer next steps and wait" step is replaced by the handoff.
Input
Same as new-issue: an optional description of what the issue should cover; with no input, derive it from the current conversation. Optionally owner/repo when the issue belongs elsewhere.
Steps
1. Run new-issue
Invoke the new-issue skill (Skill tool, skill: new-issue) with the user's description (or conversation-derived scope). Let it run its full process. Capture the created issue from its report as the full reference owner/repo#N: the repository new-issue filed to (its -R owner/repo, else the current checkout per gh repo view --json nameWithOwner -q .nameWithOwner) and the new number.
2. Stop gate — cases the loop can't safely continue
| Condition | Action |
|---|---|
| new-issue found an existing open issue/PR already covering it (no issue filed) | STOP. Report the duplicate and new-issue's offer to update/comment instead; do not merge scopes yourself. |
| The conversation held several distinct candidates | If one clearly converged, file it and continue the chain with it; the unfiled candidates go in the final report. If none clearly converged, STOP — report the candidates and ask which to file. Never bundle, never auto-file the extras. |
| new-issue split the work and named unfiled follow-ups | Continue with the core issue only; relay the unfiled follow-ups in the final report. |
Otherwise (one issue filed cleanly), continue.
3. Hand off to validate-issue-loop
Invoke the validate-issue-loop skill (Skill tool, skill: validate-issue-loop) with the step 1 owner/repo#N passed explicitly, always, whichever repository new-issue filed to. Its own scope gate (too large / infeasible / already-addressed) and its edit-landing stop still apply and may stop the run; the report relays such a stop as a stop.
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 84b9362da8fa
- 20d ago Changed 14ca262d2d5e
- 23d ago Changed abc94e7e2a9f
- 27d ago Changed · +2 lines · +8 tokens per session ab38de078b4f
- 28d ago Changed e49331404192
- 1mo ago First seen · 52 lines · 111 tokens per session scan A 8996c5d99091
new-issue-loop is a skill published in the GitHub repository richkuo/rk-skills (50 stars, last pushed 2d ago), licensed MIT. It adds 119 tokens to every session and 925 once invoked, about $0.0005 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.