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 fable-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/fable-new-issue-loop)<a href="https://agentmods.dev/skills/richkuo/rk-skills/fable-new-issue-loop"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/fable-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/fable-new-issue-loop"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/fable-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.00134 | $0.00760 |
| Opus 5 | $0.00067 | $0.00380 |
| Sonnet 5 | $0.00027 | $0.00152 |
| Haiku 4.5 | $0.00013 | $0.00076 |
Grade A, and why
fable-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 5d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fable-new-issue-loop
Chain fable-new-issue → validate-issue-loop into one autonomous run: a Fable 5.1 subagent drafts the issue, the main agent files it, and the loop drives it to a reviewed PR without a human in between.
This skill is new-issue-loop with a different front of the chain. Follow the new-issue-loop skill for the full procedure: the complete-issue rule, the input contract, the stop gate, the handoff to validate-issue-loop (explicit issue reference, owner/repo#N when filed cross-repo), the report format, and the Red Flags. Apply only the deltas below.
Deltas from new-issue-loop
- Step 1, front of the chain. Invoke the
fable-new-issueskill (Skill tool,skill: fable-new-issue) in place ofnew-issue. Let it run its full process (Fable 5.1 subagent draft, duplicate gate, spot-check, filing) and capture the created issue number from its report. - Step 2, stop gate. new-issue-loop's stop gate applies with one extra row for the Fable draft; the effective table:
| Condition | Action |
|---|---|
| fable-new-issue found an existing open issue/PR already covering it (no issue filed) | STOP. Report the duplicate and the offer to update/comment instead — merging scopes is a human call. |
| 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. |
| fable-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. |
| The draft was structurally wrong and fable-new-issue paused for a human decision | STOP. Relay what is off. Do not file or re-dispatch on your own. |
- Step 3, why validation still runs. Validating an issue this chain just filed stays useful: validate-issue re-traces the claims against the code independently and catches anything the Fable draft or the spot-check got wrong.
- Step 4, report. Mark the issue line as drafted by Fable 5.1. Cap the whole report at 55 words, plain simple English in ASD-STE100 — apply the Response Style rules in CLAUDE.md/AGENTS.md.
- One extra Red Flag. Tempted to skip the Fable subagent and draft or file the issue yourself to go faster: never. The draft coming from Fable 5.1 is the point of this skill.
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.
- 5d ago Changed · +4 tokens per session b806f94fc039
- 9d ago First seen · 26 lines · 130 tokens per session scan A 288ed1a7ed25
fable-new-issue-loop is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed today), licensed MIT. It adds 134 tokens to every session and 760 once invoked, about $0.0007 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
loop-it
An automated workflow that repeatedly fetches open GitHub issues, orders them by dependencies, implements them, reviews the changes, and ships them.
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.
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"…
dependabot
Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update…
github-release
Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.
brag-sheet
Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works…