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 issueplangit 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/issueplan)<a href="https://agentmods.dev/skills/richkuo/rk-skills/issueplan"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/issueplan/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/issueplan"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/issueplan.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.00080 | $0.01194 |
| Opus 5 | $0.00040 | $0.00597 |
| Sonnet 5 | $0.00016 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
issueplan 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issueplan
The current session's large language model (LLM) plans and builds. Never call the Agent tool, Task tool, workflow delegation, or any subagent mechanism at any step.
Input
A task description, with an optional GitHub issue:
- Prose, such as "issueplan adding X to Y".
- An issue reference: full URL,
#<N>, bare<N>, orowner/repo#N. The plan is then also posted as an issue comment. - Ask what to plan only when the task is unclear. With no issue referenced, never invent one or post anywhere.
Steps
1. Resolve the GitHub issue (only if one is referenced)
Fetch the issue before planning:
gh issue view <N> --json number,title,body,url
Add -R owner/repo for another repository. Stop and tell the user if the command fails. Never plan from a paraphrase of an issue you could not fetch.
Record the number, URL, title, and full body for steps 2 and 4. Read any ## Execution block as a task constraint. Planning still runs on the current session model and effort.
2. Produce the plan in the current session
Inspect the repository with read-only commands. Read its instruction files and the code that controls the requested behavior.
Produce a concrete, ordered plan: files to create or modify, the approach, build sequence, correctness and safety risks, edge cases, and verification. Number the implementation steps (1., 2., …) and end each step with a verify point: the observable check that proves the step is done (a command, a passing test, a file state).
Plan the absolute-best solution. Cost, time, token use, and code volume never narrow the option space. Only correctness and safety override "best".
Write the plan in clean Markdown, fit to act on directly and to post verbatim as an issue comment. Save it to a scratchpad file at once. It must survive context summarization during a long build, and step 4 posts from it.
3. Check the plan against the code
Verify each load-bearing claim: the files, symbols, commands, and conventions the plan names exist. Fix small errors yourself, note them, and update the scratchpad file. If the plan depends on a missing mechanism or a major false assumption, stop and ask the user whether to revise the task or the plan.
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.
- 5d ago Changed · -57 lines cf8e30023c8c
- 9d ago First seen · 138 lines · 80 tokens per session scan A b4b2b9e7e376
issueplan is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,194 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
contradiction-analysis
A structured way to analyze difficult problems by identifying competing forces, finding the main conflict, and deciding which side or issue has the greatest effect.
mass-line
A method for collecting feedback and facts from multiple people or sources, turning them into a plan, and checking the plan with those affected.
concentrate-forces
A decision-making method for situations where several tasks compete for limited time, attention, computing power, or budget.
practice-cognition
A method for testing ideas in practice, learning from the results, and improving the next attempt through repeated cycles.
protracted-strategy
A long-term planning method for difficult work that cannot be completed quickly, divided into stages with steady progress over time.
arming-thought
A Chinese-language routing guide built around checking facts before drawing conclusions. It helps select other methods for tasks such as investigation, decision-making, review, and long-term planning.