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/pronskiy/php-src-developer/review-localnpx skills add pronskiy/php-src-developer --skill review-localgit clone --depth 1 https://github.com/pronskiy/php-src-developerWhat 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.00102 | $0.01722 |
| Opus 5 | $0.00051 | $0.00861 |
| Sonnet 5 | $0.00020 | $0.00344 |
| Haiku 4.5 | $0.00010 | $0.00172 |
Grade A, and why
review-local 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-local
Review the user's current local php-src diff. Read-only. Produces REVIEW.md in pwd.
Inputs
$PHP_SRC_DIR— the php-src checkout.- Optional base ref — defaults to
git merge-base HEAD origin/master. User can override (/review-local PHP-8.3). - The skill operates against the current branch in
$PHP_SRC_DIR. It does NOT switch branches.
What it produces
REVIEW.mdin the task directory resolved per_shared/task-dir.md(default$PHP_SRC_DIR/.claude/php-core-dev/review-<short-base>/REVIEW.md) — severity-graded findings.- If
REVIEW.mdexists from a prior run at the same path, it's backed up toREVIEW.md.bakbefore being overwritten. - Slug:
review-<short-sha>where<short-sha>isgit rev-parse --short <base>. If the base is a branch (e.g.PHP-8.3— any maintained branch from_shared/branch-detection.md), usereview-<branch-slug>instead. Slug is written to.current.
Workflow
1. Pre-checks
test -n "$PHP_SRC_DIR" && test -d "$PHP_SRC_DIR/Zend" || { echo "Run /install"; exit 1; }
cd "$PHP_SRC_DIR"
git status --porcelain # warn (don't block) if dirty
If the working tree is dirty, note it in REVIEW.md's Scope section — uncommitted changes are part of the diff to review.
2. Determine base ref
BASE=$(git merge-base HEAD origin/master 2>/dev/null || git merge-base HEAD master)
If the user passed an explicit base (PHP-8.3, a SHA, etc.), use that.
If no base can be determined (no master, no origin), stop with:
Cannot determine review base. Pass one explicitly: /review-local <base-ref>
3. Pull the diff
git -C "$PHP_SRC_DIR" diff "$BASE"...HEAD --stat
git -C "$PHP_SRC_DIR" diff "$BASE"...HEAD
Capture:
- Files changed (count, paths)
- Lines added / removed (from
--stat) - The full unified diff (for analysis)
If the diff is empty, stop with No changes between $BASE and HEAD — nothing to review.
4. Backup existing REVIEW.md
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 · 139 lines · 102 tokens per session scan A 14ed341d2d2b
review-local is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 3mo ago), licensed MIT. It adds 102 tokens to every session and 1,722 once invoked, about $0.0005 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…