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 agentmods add skills/richkuo/rk-skills/github-issue-formatnpx skills add richkuo/rk-skills --skill github-issue-formatgit clone --depth 1 https://github.com/richkuo/rk-skillsWhat 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 | $0.00051 | $0.00777 |
| Opus 5 | $0.00026 | $0.00388 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
github-issue-format 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 3d 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.
What it actually says
GitHub issue format
- Never create a placeholder, stub, or empty-bodied issue. Every issue gets a complete body at creation — complexity rationale line, concrete problem statement, goal, approach/acceptance criteria,
## Plain simple English— even in a batch. If a follow-up isn't ready to spec, track it in the parent issue or notes until it is. - Title format:
[C<score>] <title>— a clear plain-simple-English sentence in ASD-STE100, precise about component and behavior, e.g.[C95] Orders can be filled twice when two fills arrive at the same moment. - Complexity score (0–100) is a model + effort routing signal. It is not a time estimate. Load the canonical formula, axes, and routing table from
validate-issuestep 6; do not restate or approximate them here. - First line of the body is a one-line rationale matching the title prefix, ending with an explicit fableplan signal:
**Complexity: 95/100** — Capability 3 (Risk 4 — money/data-integrity on order-fill path); Volume 20 — Opus 5, xhigh · fableplan: yes(Fable 5 never pairs withxhigh; the LLM Attribution Footer section of CLAUDE.md owns the Fable effort ceiling. xhigh is legal only on Opus/Sonnet-class builds.) - fableplan signal:
· fableplan: yeswhen the score is ≥ 71 (a Fable 5 plan is posted before the build; the builder is Opus 5 at both plan bands: high at 71–80, xhigh at 81+); scores below 71 are· fableplan: no(they don't need a separate plan). Always write it explicitly — absence is ambiguous, not "no". - Body section order: complexity rationale line,
## Problem,## Goal,## Approach,## Acceptance criteria,## Plain simple English, then any Execution block, then the attribution footer.Plain simple Englishis the last prose section a human reads; an Execution block is machine metadata and keeps its place between that section and the footer. ## Plain simple Englishis mandatory on every issue. One short paragraph under 55 words in ASD-STE100 (Simplified Technical English) per the CLAUDE.md/AGENTS.md Response Style rules. State what is wrong or missing and why it matters, so a reader who knows the product but not the code understands the issue without reading the technical sections. Never restate the approach there, never list file paths or symbols, and never put a time or effort estimate in it. An edit that rewrites body prose adds the section when it is missing; an edit that changes only machine metadata (the Execution block, or the[C<score>]title prefix) leaves every prose section unchanged and does not add it.- End the body with the LLM Attribution Footer —
Createdfor a new issue,Validatedwhen a validation pass produced the edit (validate-issueand its wrappers),Updatedfor any other edit. Stack the new line under the existing ones; never replace them, and never append a line that exactly duplicates one already there. - Project precedence: a repo CLAUDE.md issue/footer format overrides this default.
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.
- 3d ago First seen · 19 lines · 51 tokens per session scan A 22a8d9d3cffb
github-issue-format is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 777 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
criticism-self-criticism
触发：当一项工作已经完成、进入阶段验收、收到批评反馈，或反复出现同类错误需要系统纠偏时调用；常见信号包括 review、audit、retrospective、quality check、纠错与复盘。 English: Trigger after delivery or at a review checkpoint when quality must be examined honestly and errors must be corrected without defensiveness. Use this skill for structured self-review, feedback processing, and…
mass-line
触发：当你需要收集多方意见、把零散反馈整合成可执行方案，或把方案带回真实使用者/执行者验证时调用；常见信号包括 stakeholder input、user feedback、意见汇总、对齐与验证。 English: Trigger when input must be gathered from many people, synthesized into a clearer plan, and returned to the affected users or executors for validation. Use this skill for a collect-synthesize-validate loop.
workflows
触发：当你面临的任务明显需要多个思想武器协作时调用；常见信号包括：从零启动新项目、攻坚复杂疑难问题、对已有方案进行迭代优化。此 skill 提供标准化的跨 skill 工作流组合，解决"应该先用哪个 skill、怎么衔接"的问题。 English: Trigger when a task clearly requires multiple skills in sequence. Use this skill to select a standard workflow that chains skills together, defines data handoff between steps, and specifies…
investigation-first
触发：当你准备下判断、做决策或提出建议，但事实、上下文或一手信息还不充分时优先调用；常见信号包括 unknowns、信息缺口、证据不足、领域陌生、需要先摸清现状。 English: Trigger before making claims or decisions when context is incomplete, evidence is weak, or the domain is unfamiliar. Use this skill to investigate first, gather firsthand facts, and let reality shape the conclusion.
overall-planning
触发：当你需要在多个目标、利益方或相互制约的指标之间做动态平衡时调用；常见信号包括 trade-offs、目标冲突、系统性约束、优化一项会伤害另一项。 English: Trigger when several important goals must be advanced together and optimizing one dimension can damage another. Use this skill to map the key relationships, avoid one-sided decisions, and balance the system as a whole.
protracted-strategy
触发：当目标长期、任务复杂、资源暂时处于劣势，或短期无法速胜但又不能放弃时调用；常见信号包括 long-term effort、phased plan、endurance、战略耐心、需要分阶段推进。 English: Trigger when the work is long-horizon, difficult, and unlikely to be won quickly. Use this skill to divide the effort into stages, keep strategic confidence, and accumulate small wins into overall victory.