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 validate-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/validate-issue)<a href="https://agentmods.dev/skills/richkuo/rk-skills/validate-issue"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/validate-issue.svg" alt="Measured on agentmods" 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.00034 | $0.02674 |
| Opus 5 | $0.00017 | $0.01337 |
| Sonnet 5 | $0.00007 | $0.00535 |
| Haiku 4.5 | $0.00003 | $0.00267 |
Grade A, and why
validate-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 2d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
validate-issue
Validate every current-behavior claim against code. Input: an issue URL, #N, N, or owner/repo#N; with none, take the newest open issue and state its number. { issue: <N>, targetBranch?: "<branch>" } (or prose "target branch ") names the merge target, which replaces the default branch in step 0.
0. Baseline branch
No worktree for validation or issue edits. Resolve DEFAULT=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name); with a targetBranch, validate it per work-on-issue step 1 ("Target"), set DEFAULT to it, and name it as the target in the verdict. Run git fetch origin "$DEFAULT"; the verdict states git rev-parse --short "origin/$DEFAULT" as the baseline. Read a working-tree path only when it is tracked and git diff --quiet "origin/$DEFAULT" -- <path> exits 0; otherwise read git show "origin/$DEFAULT":<path>.
1. Fetch the issue and linked PRs
Run gh issue view <N> --comments, then list the cross-referenced PRs that comments omit (owner/repo#N input names the repo):
gh api --paginate repos/{owner}/{repo}/issues/<N>/timeline --jq '.[] | select(.event=="cross-referenced") | .source.issue | select(.pull_request) | "\(.number) \(.state)"'
Verify a merged fix against current code and recommend closure or reuse; list open overlapping PRs under Concerns.
2. Extract claims and assertions
List each current-behavior claim (causes, citations, sets, negatives, benefit premises) and proposal assertion (goals, lifetime, population timing, benefits, consumers, failure policy, deployment surface, touched sites). Flag for 5a and 5b: a new subsystem, shared state, cross-cutting refactor, deduplication, single source of truth, multi-consumer coordination, or infrastructure analogy.
3. Verify claims
Trace each scenario through its conditions and config. Code outranks prose. Verify independently even for the repo owner, recent code, or runtime state machines. Apply every triggered depth rule:
What ships with it
4 files 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.
- 2d ago Changed c8d9ca8f8c52
- 3d ago Changed 4469c80fa3fe
- 4d ago Changed · -41 lines · -27 tokens per session 98da16ef9f92
- 8d ago First seen · 190 lines · 61 tokens per session scan A 0ae3945e3dde
validate-issue is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,674 once invoked, about $0.0002 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
A structured review method for examining completed work, criticism, and repeated mistakes. It focuses on specific evidence, causes, effects, and practical improvements.
refactor
Expert code refactoring based on Martin Fowler's catalog — improve maintainability without changing behavior. Covers code smells, composing methods, moving features, organizing data, simplifying conditionals, method calls, and generalization. Triggers on: refactor, 重构, clean up, improve code, code smell, extract…
understand
Review and understand freshly AI-generated code. Scans the current repo's uncommitted/branch changes and builds a Claude-style light-themed two-column webpage — left is the project folder tree of changed files, right is the selected file's syntax-highlighted diff (additions/deletions clearly distinguished from…
arize-annotation
INVOKE THIS SKILL when creating, managing, or using annotation configs or annotation queues on Arize (categorical, continuous, freeform), or applying human annotations to project spans via the Python SDK. Configs are the label schema for human feedback; queues are review workflows that route records to annotators.…
ai-ready
Make any repo AI-ready — analyzes your codebase and generates AGENTS.md, copilot-instructions.md, CI workflows, issue templates, and more. Mines your PR review patterns and creates files customized to your stack. USE THIS SKILL when the user asks to "make this repo ai-ready", "set up AI config", or "prepare this repo…
dotnet-best-practices
Ensure .NET/C# code meets best practices for the solution/project.