Borrowing it
Nothing to install: this file belongs to arraydude/agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arraydude/agent-skills/main/.claude/commands/validate-pr.mdgit clone --depth 1 https://github.com/arraydude/agent-skillsWrote 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/commands/arraydude/agent-skills/validate-pr)<a href="https://agentmods.dev/commands/arraydude/agent-skills/validate-pr"><img src="https://agentmods.dev/badge/commands/arraydude/agent-skills/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/commands/arraydude/agent-skills/validate-pr"><img src="https://agentmods.dev/badge/commands/arraydude/agent-skills/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.00909 |
| Opus 5.5 | $0.00008 | $0.00364 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
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 2mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal: Validate AI PR comments on the current branch.
PR URL: $ARGUMENTS
Prerequisites
- Check if GH CLI is installed:
- Run
which ghto verify the GitHub CLI is available - If not installed, stop and ask the user to install it:
- macOS:
brew install gh - Then authenticate:
gh auth login
- macOS:
- Run
Input Validation
- Validate PR argument:
- If
$ARGUMENTSis empty or missing, display this error and stop:Error: Please provide a PR number or URL. Usage: /validate-pr <PR_NUMBER_OR_URL> Examples: /validate-pr 123 /validate-pr https://github.com/owner/repo/pull/123 - Accept either:
- PR number (e.g.,
123) - Full PR URL (e.g.,
https://github.com/owner/repo/pull/123)
- PR number (e.g.,
- Extract the PR number from the URL if a full URL is provided
- If
Instructions
-
Fetch PR information using GH CLI:
- Extract the PR number from the provided URL
- Run
gh pr view <PR_NUMBER> --json comments,reviews,body,title,filesto get all PR data - List all comments and review comments on the PR
-
Think critically about each comment:
- AI-generated comments may contain hallucinations or incorrect assumptions
- For each comment, verify:
- Is the referenced code/file actually present in the PR diff?
- Is the assumption or concern actually valid?
- Does the suggested fix make sense in context?
-
Cross-reference with actual code:
- Use
gh pr diff <PR_NUMBER>to see the actual changes - Read the relevant files to understand the full context
- Check if the AI comment misunderstood the code intent
- Use
-
Evaluate if issues are worth addressing:
- Even if an assumption is technically true, assess:
- Is it a real problem or a theoretical edge case?
- Does fixing it add value or just noise?
- Is it aligned with project patterns and conventions?
- Even if an assumption is technically true, assess:
-
Double-check for missed comments:
- PRs often have many comments - make sure you reviewed ALL of them
- Check both general PR comments and inline review comments
- Use
gh api repos/<owner>/<repo>/pulls/<pr_number>/commentsif needed for complete coverage
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.
- 2mo ago First seen · 101 lines · 19 tokens per session scan A a048b2ef7db7
validate-pr is a command published in the GitHub repository arraydude/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 909 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-08-31.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
refactor
Systematic code refactoring with smart scope detection.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).