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 fableplan-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/fableplan-work-on-issue)<a href="https://agentmods.dev/skills/richkuo/rk-skills/fableplan-work-on-issue"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/fableplan-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/fableplan-work-on-issue"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/fableplan-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.00055 | $0.00983 |
| Opus 5 | $0.00028 | $0.00491 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
fableplan-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 6d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fableplan-work-on-issue
Chain fableplan → work-on-issue into one autonomous run: Fable 5.1 plans the implementation for a GitHub issue (plan posted to the issue), then work-on-issue implements that plan in an isolated worktree and opens a PR that closes the issue.
This is fableplan-loop with the review loop removed — the handoff is to work-on-issue (single-shot, ends at the open PR) rather than work-on-issue-loop (which triggers @claude and cycles through review). Like fableplan-loop, it has no validate-issue step and no score gate: with no validation to produce a score, fableplan always runs. Reach for this when you already trust the issue and just want a Fable-vetted plan built and shipped as a PR, without paying for validation or driving review to convergence.
Input
Same as fableplan-loop: a GitHub issue is required; with nothing supplied, default to the latest open issue in the current repo. If no issue can be resolved, stop and ask — do not plan or implement against a paraphrase.
Optional targetBranch (orchestration form { issue, targetBranch } or a prose "target branch "): passed unchanged to every validate, plan, and build step in the chain, so the baseline and the PR base are that branch instead of the repo default. work-on-issue step 1 ("Target") owns its validation.
Steps
Follow fableplan-loop steps 0 through 3 with these changes:
- Step 0 (pre-plan gate) applies unchanged.
- Step 1 (fableplan): instruct fableplan to use the harness suffix
fableplan-work-on-issuein the posted comment's attribution footer. - Step 2 (handoff): invoke the
work-on-issueskill instead ofwork-on-issue-loop(Skill tool,skill: work-on-issue). The explicit issue-number pass-through and the plan pointers (scratchpad file and posted issue comment) apply unchanged, and deviations followwork-on-issuestep 2's plan-deviation policy — each named in the PR body. work-on-issue runs its full process: it implements in a fresh worktree, verifies, commits, pushes, and opens a PR that closes the issue. It ends at the open PR — requesting review is out of scope for this skill. If the user wants the PR driven through review to convergence, that'sfableplan-loop(this chain plus the review loop),validate-fableplan-loop, or a separatefix-pr-review-looprun; say so rather than triggering review here. - Step 3 (report): relay work-on-issue's final summary (the worktree/branch, what was implemented, the verification result, the commit SHA, the PR URL, and that it closes the issue), prefixed with one line covering the head of the chain: plan posted (comment URL). If work-on-issue stopped at one of its own gates instead of opening a PR, report why it stopped — never imply a PR exists when it doesn't. Cap the whole report at 55 words, plain simple English in ASD-STE100 — apply the Response Style rules in CLAUDE.md/AGENTS.md.
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.
- 6d ago Changed · +2 lines · +2 tokens per session f3d3e93a5142
- 10d ago First seen · 32 lines · 53 tokens per session scan A 2a9a197d180b
fableplan-work-on-issue is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 983 once invoked, about $0.0003 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"…
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…
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…