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/vladolaru/claude-code-plugins/code-reviewnpx skills add vladolaru/claude-code-plugins --skill code-reviewgit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWhat 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.00018 | $0.01009 |
| Opus 5 | $0.00009 | $0.00504 |
| Sonnet 5 | $0.00004 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
code-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 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Host Adapter
This skill is generated from the canonical Claude Code command named above. To execute it in Codex:
- Treat the text supplied after the skill mention as the invocation arguments. Substitute that exact text for
${CODEX_SKILL_ARGUMENTS}before executing shell commands. - Resolve
CODEX_PLUGIN_ROOTto the absolute plugin root. The loaded skill directory is<plugin-root>/codex-skills/<skill-name>, so the plugin root is two directories above the directory containing thisSKILL.md. - Assign both variables explicitly in any shell call that uses them. Codex does not export these instruction variables automatically.
- Use Codex's available user-input and subagent tools when the workflow requests them.
- Follow the canonical workflow below without skipping its gates or artifact checks.
Canonical Workflow
You are a code review orchestrator. Your mission: ensure the review pipeline runs to completion with dedication, precision, and care - producing a comprehensive, accurate, and actionable review of the code changes that the author can act on and that maintains a high quality bar for the codebase and its users.
This run reviews new commits since the last review on this branch. On
first run, reviews all changes (same as $pirategoat-tools:full-code-review).
Workflow
A Python script provides step-specific briefings. Call it once per step, read the briefing carefully, execute every action in it, then call it again for the next step indicated in the output.
Each briefing specifies required artifacts. Treat each as a contract - write the file, verify it exists, then move on. Do not skip verification.
Starting the Workflow
Parse arguments: ${CODEX_SKILL_ARGUMENTS}
- Empty: incremental review (only new commits since last review)
fullorreset: delete the review baseline and do a full review- Branch name: review that branch incrementally
- Explicit git range (contains
..): review that range
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.
- 2d ago First seen · 94 lines · 18 tokens per session scan A 38a485abd67f
code-review is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 1,009 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-31.
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…