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/base/skills/plugin-reviewnpx skills add base/skills --skill plugin-reviewgit clone --depth 1 https://github.com/base/skillsWhat 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.00095 | $0.01166 |
| Opus 5 | $0.00048 | $0.00583 |
| Sonnet 5 | $0.00019 | $0.00233 |
| Haiku 4.5 | $0.00010 | $0.00117 |
Grade A, and why
plugin-review scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://raw.githubusercontent.com/base/skills/master/skills/base-mcp/references/plugin-spec.md How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Review
Validate Base MCP plugin files against the current Plugin Specification. Produces a conformance report with actionable findings.
Works for both authors (self-check before submitting a PR) and reviewers (evaluate an incoming PR).
Workflow
-
Fetch the current spec (it changes — never rely on a stale copy):
curl -s https://raw.githubusercontent.com/base/skills/master/skills/base-mcp/references/plugin-spec.mdRelated docs worth reading:
references/custom-plugins.md,references/approval-mode.md,references/batch-calls.md, andSKILL.md(the root skill). Existing native plugins underskills/base-mcp/plugins/are the precedent for conventions. -
Read the plugin file in full. If reviewing a PR:
gh pr view <n> --repo base/skills --json title,body,number,headRefName,files,additions,deletions gh pr diff <n> --repo base/skills # raw plugin file (diff may be truncated): gh api "repos/base/skills/pulls/<n>/files" --jq '.[] | select(.filename|endswith(".md")) | .raw_url' -
Static conformance evaluation — assess against every dimension in
references/evaluation-criteria.md(includes compliance/language checks and high-risk category gates). Write the report usingreferences/report-template.md. -
(Optional) Live API / SDK verification — exercise the documented endpoints/SDK/contracts with read-only calls. See
references/live-testing.md. For perps/prediction-market/gambling plugins, also run the geoblock verification (compare frontend vs API access restrictions). Append a## Live API / SDK Verificationsection to the report. This routinely overturns doc claims (fabricated/locked endpoints, broken hosts, wrong response shapes). -
Save the report. If reviewing a PR and asked to comment, draft a PR comment from the report using
references/comment-guidelines.mdand post with:gh pr comment <n> --repo base/skills --body-file <comment-file>.
Multiple PRs
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.
- yesterday First seen · 52 lines · 95 tokens per session scan A 81fcf80b4121
plugin-review is a skill published in the GitHub repository base/skills (114 stars, last pushed 8d ago), licensed MIT. It adds 95 tokens to every session and 1,166 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…