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 Abilityai/abilities --skill validate-prgit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/validate-pr)<a href="https://agentmods.dev/skills/abilityai/abilities/validate-pr"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/validate-pr/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/abilityai/abilities/validate-pr"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/validate-pr.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.00019 | $0.01160 |
| Opus 5.5 | $0.00008 | $0.00464 |
| Sonnet 5.5 | $0.00004 | $0.00232 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
validate-pr 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Pull Request
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.validate-pr vX.Y — recent: <summary>. Then proceed.
Validate a pull request against the project development methodology and generate a merge decision report.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| PR Details | GitHub API | ✅ | PR metadata and diff | |
| Changelog | docs/memory/changelog.md |
✅ | Entry check | |
| Requirements | docs/memory/requirements.md |
✅ | Req updates | |
| Architecture | docs/memory/architecture.md |
✅ | API changes | |
| Feature Flows | docs/memory/feature-flows/ |
✅ | Flow updates | |
| GitHub Issues | GitHub repo | ✅ | Issue references |
Usage
/validate-pr <pr-number-or-url>
Process
Step 1: Fetch PR Information
PR_NUMBER=<extract number from argument>
gh pr view $PR_NUMBER --json title,body,author,baseRefName,headRefName,files,additions,deletions,changedFiles
gh pr diff $PR_NUMBER --name-only
gh pr diff $PR_NUMBER
Step 2: Validate Documentation Updates
2.1 Changelog Entry (REQUIRED)
Check if docs/memory/changelog.md is in the changed files list.
- Entry at TOP of recent changes
- Has timestamp format:
### YYYY-MM-DD HH:MM:SS - Has emoji prefix
- Includes summary of what changed and why
If missing: Flag as FAIL - "Changelog not updated"
2.2 GitHub Issues Update (CONDITIONAL)
Check if PR references a GitHub Issue.
2.3 Requirements Update (CONDITIONAL)
Required if PR adds new functionality or changes feature scope.
2.4 Architecture Update (CONDITIONAL)
Required if PR modifies API endpoints, database schema, or external integrations.
Step 3: Validate Feature Flows
- Check for feature flow changes in diff
- If feature behavior changed but no flow updated: Flag as WARNING
- Validate feature flow format (required sections, file paths with line numbers)
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 · 148 lines · 19 tokens per session scan A 24f31042d8c4
validate-pr is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 1,160 once invoked, about $0.0001 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-09-07.
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…