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/policyengine/policyengine-claude/review-programnpx skills add PolicyEngine/policyengine-claude --skill review-programgit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWhat 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.00061 | $0.00580 |
| Opus 5 | $0.00030 | $0.00290 |
| Sonnet 5 | $0.00012 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
review-program 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.
What it actually says
review-program
Thin launcher. The canonical workflow — phases, roles, gates, severity rules, artifact contracts — lives in references/workflow.md. Read it completely before acting and follow it exactly; this file only adapts it to this surface. Do not redefine flags, phases, severity rules, file ownership, or completion gates here.
Use this skill for PolicyEngine-specific PR reviews even when the user starts from a
generic built-in review command (such as Codex /review): the canonical workflow adds
PolicyEngine source, reference, regulatory, PDF, and test-review rules a generic review
lacks.
Treat the text after $review-program or /review as the raw workflow arguments:
$review-program [PR_NUMBER_OR_SEARCH] [PDF_URL] [--local] [--local-diff] [--full]
[--skip-pdf] [--600dpi] [--resume] [--incremental REPORT] [--prefix NAME]
Mandatory completion gate:
- Do not stop after individual validators or PDF audits.
- The review is incomplete until
{RUN_ROOT}/{PREFIX}-review-full-report.mdand{RUN_ROOT}/{PREFIX}-review-summary.mdboth exist. - Phase 6 consolidation is required before displaying or posting findings.
Surface adapters:
- Claude Code: also read references/claude-launcher.md — it maps canonical roles to this plugin's agent types and the workflow's abstract operations to Claude Code mechanics.
- Codex: use the delegation mapping below.
Delegation mapping (when subagent use is available and authorized):
- Map every role in the canonical Roles table to a
workerwhen it writes report or artifact files, or anexplorerfor read-only codebase questions. - Pass concrete
RUN_ROOT,WORKTREE_ID, andPREFIXvalues and the role's task spec from the canonical workflow to every subagent; name the role's skills explicitly in the subagent prompt — do not assume a worker infers them from parent context. - Every subagent finishes by writing its assigned file and returning the one-line DONE message from the canonical completion contract.
- If subagents are unavailable or not authorized, execute the roles directly in phase order, preserving the same handoff files and read-only contract.
What ships with it
2 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 First seen · 53 lines · 61 tokens per session scan A abd3970ff285
review-program is a skill published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 580 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…