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 codex-validate-plan-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/codex-validate-plan-work-on-issue)<a href="https://agentmods.dev/skills/richkuo/rk-skills/codex-validate-plan-work-on-issue"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/codex-validate-plan-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/codex-validate-plan-work-on-issue"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/codex-validate-plan-work-on-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00230 | $0.04001 |
| Opus 5.5 | $0.00092 | $0.01600 |
| Sonnet 5.5 | $0.00046 | $0.00800 |
| Haiku 4.5 | $0.00023 | $0.00400 |
Grade A, and why
codex-validate-plan-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 14d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codex-validate-plan-work-on-issue
Run validate, plan, and build for one or more issues at the same time. Each issue is its own pipeline and advances the moment its own previous stage ends, whatever the other issues are doing. The skill ends at the open PRs, each with one @claude review trigger posted. It waits for no review and fixes nothing. fix-pr-review-loop drives a PR through review.
Report length, wording, and formatting follow the Response Style section of CLAUDE.md/AGENTS.md. This skill restates none of it.
The scripts, the prompt templates, and the check scripts are in run-recipes.md. Read it completely before step 1. The session is the driver named in cli-dispatch section 9, so read that section completely too: this skill reuses its validate shim, its limits, its snapshot guard, and its issue check.
Input
- Issues: one or more of
#<N>,<N>, orowner/repo#N, or a request for "the next N parallel issues" (step 0). With neither, ask once. - Stage models and effort: the defaults below apply unless the request names others.
| Stage | Default | Runs through |
|---|---|---|
| Validate | Sol 6.1 (Codex CLI, gpt-6.1-sol) at high |
cli-dispatch section 9 validate pass, update mode |
| Plan | Sol 6.1 (Codex CLI, gpt-6.1-sol) at high, a separate Codex run |
issueplan in-session mode, on the same read-only shim |
| Build | Opus 5.5 at high, a background subagent |
work-on-issue |
- A Codex stage takes a display name plus an explicit model id.
cli-dispatchsection 2 owns the id rules and blocks a name with no id. Before the first launch, check each Codex stage's id and tier against the catalog the Codex CLI reports:codex debug models | jq -e --arg id "$MODEL_ID" --arg tier "$TIER" 'any(.models[]; .slug == $id and any(.supported_reasoning_levels[]?; .effort == $tier))'. Any output other thantrue, or a failed command, blocks the run. - The build model is Opus 5.5 or Sonnet 5.5 (Agent
modelvalueopusorsonnet). A Fable, Codex CLI, or Cursor CLI build belongs tofable-dispatch,cli-dispatch, ormilestone-pipeline. - An issue's
Validate model:andBuild model:stamps are not read. The request and the defaults above decide. When an issue stamps an external build harness, say so in the report. - Optional
targetBranchreplaces the default branch as the traced ref and passes unchanged tovalidate-issue,issueplan, andwork-on-issue.
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.
- 14d ago First seen · 116 lines · 230 tokens per session scan A bbf09d7da313
codex-validate-plan-work-on-issue is a skill published in the GitHub repository richkuo/rk-skills (50 stars, last pushed 2d ago), licensed MIT. It adds 230 tokens to every session and 4,001 once invoked, about $0.0009 per session on Opus 5.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-10-12.
Other skills, from other repositories
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"…
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.