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 kdcokenny/ocx --skill plan-reviewgit clone --depth 1 https://github.com/kdcokenny/ocxWrote 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/kdcokenny/ocx/plan-review)<a href="https://agentmods.dev/skills/kdcokenny/ocx/plan-review"><img src="https://agentmods.dev/badge/skills/kdcokenny/ocx/plan-review/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/kdcokenny/ocx/plan-review"><img src="https://agentmods.dev/badge/skills/kdcokenny/ocx/plan-review.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.00011 | $0.01037 |
| Opus 5 | $0.00005 | $0.00518 |
| Sonnet 5 | $0.00002 | $0.00207 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
plan-review 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plan-review — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review
Load this skill when reviewing implementation plans (not code).
TL;DR
Systematic plan review focused on 3 quality categories: Citation Quality, Completeness, and Actionability. Structure is pre-validated by plan_save—focus on whether the plan provides actionable implementation guidance.
When to Use This Skill
- When reviewing implementation plans before execution
- When auditing plan quality after creation
- When verifying plans meet documentation standards
- As part of the plan validation workflow
Plan Review Checklist
1. Structure (Pre-validated)
Note: Saved plans are structurally validated by
plan_savebefore storage. Format compliance (YAML frontmatter, status markers, CURRENT marker, numbering) is guaranteed. Focus your review on the quality aspects below.
2. Citation Quality
| Requirement | Check |
|---|---|
| Decisions reference sources | ref:delegation-id format used |
| No unsubstantiated claims | Architectural decisions cite research |
| Research phases show refs | Completed research tasks include citations |
| Citations are verifiable | IDs match actual delegation outputs |
Red Flags:
- Decisions table with empty or
-in Source column - Claims like "industry standard" or "best practice" without citation
- Research tasks marked complete without
→ ref:id
3. Completeness
| Requirement | Check |
|---|---|
| Goal is specific | Measurable outcome, not vague intent |
| Phases are logical | Sequential, with clear progression |
| Edge cases considered | Error handling, failure modes addressed |
| Notes section present | Key decisions and observations documented |
| Context & Decisions table | Captures architectural choices with rationale |
Goal Quality Examples:
- ❌ "Improve authentication" (vague)
- ❌ "Make it better" (unmeasurable)
- ✅ "Add JWT authentication with refresh token support" (specific)
- ✅ "Migrate user table to PostgreSQL with zero downtime" (measurable)
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.
- 9d ago First seen · 153 lines · 11 tokens per session scan A 73a2c9310024
plan-review is a skill published in the GitHub repository kdcokenny/ocx (938 stars, last pushed 21d ago), licensed MIT. It adds 11 tokens to every session and 1,037 once invoked, about $0.0001 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
cli-builder
Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.
contract-integrity
Maintains an Agulater Agent Operational Contract after agent files change. Use when changing AGENTS.md, harness policy, graphs, skills, context layers, evaluation, or handoff behavior.
change-safety
Plans small software changes, protects existing work, and selects proportionate verification.
task-orientation
Turns a new request into a bounded task by selecting context, naming uncertainty, and defining verification. Use at the start of a new task or after a material task change.
evidence-synthesis
Builds research findings from inspected sources while preserving uncertainty and provenance.
imaging-data-commons
Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.