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 pronskiy/php-src-developer --skill review-localgit clone --depth 1 https://github.com/pronskiy/php-src-developerWrote 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/pronskiy/php-src-developer/review-local)<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/review-local"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/review-local/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/pronskiy/php-src-developer/review-local"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/review-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00102 | $0.01722 |
| Opus 5.5 | $0.00041 | $0.00689 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4mo ago), licensed MIT. It adds 102 tokens to every session and 1,722 once invoked, about $0.0004 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…