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 oguzsh/claudey --skill pr-review-approvegit clone --depth 1 https://github.com/oguzsh/claudeyWrote 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/oguzsh/claudey/pr-review-approve)<a href="https://agentmods.dev/skills/oguzsh/claudey/pr-review-approve"><img src="https://agentmods.dev/badge/skills/oguzsh/claudey/pr-review-approve/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/oguzsh/claudey/pr-review-approve"><img src="https://agentmods.dev/badge/skills/oguzsh/claudey/pr-review-approve.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.00053 | $0.01000 |
| Opus 5 | $0.00026 | $0.00500 |
| Sonnet 5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
pr-review-approve 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 12d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review and Approve
Automated PR review via code-reviewer agent with conditional gh pr review --approve.
Workflow
Step 1: Parse PR Identifier
Extract PR number from user input. Accepted formats:
123or#123(PR number)https://github.com/owner/repo/pull/123(full URL)owner/repo#123(shorthand)
If no argument provided, detect from current branch: gh pr view --json number -q .number
Step 2: Save Current Branch
ORIGINAL_BRANCH=$(git rev-parse --abbrev-ref HEAD)
Store for restoration in Step 10.
Step 3: Validate gh Authentication
gh auth status
If not authenticated, show:
Not authenticated. Run
gh auth loginto authenticate, then retry.
Stop here if auth fails.
Step 4: Fetch PR Metadata
gh pr view <NUMBER> --json number,title,author,baseRefName,headRefName,url,state
If PR not found or closed, show error and stop. Display PR title, author, and branch info to user.
Step 5: Checkout PR Branch
gh pr checkout <NUMBER>
If checkout fails, show the git error and stop. Do NOT force-checkout.
Step 6: Run Code-Reviewer Agent
Dispatch claudey:code-reviewer agent with prompt:
Review the changes in this PR. Run
git diff <baseRefName>...HEADto see all changes. Apply the full review checklist. End with the Review Summary table showing CRITICAL, HIGH, MEDIUM, LOW counts and verdicts.
Step 7: Parse Review Results
From the code-reviewer output, extract severity counts:
| Severity | Count |
|---|---|
| CRITICAL | N |
| HIGH | N |
| MEDIUM | N |
| LOW | N |
Step 8: Determine Approval Eligibility
Eligible for approval (all must be true):
- CRITICAL = 0
- HIGH = 0
- MEDIUM = 0
LOW issues are informational and do not block approval.
Not eligible: Any MEDIUM, HIGH, or CRITICAL issue found.
Step 9: Show Summary and Ask User
If eligible, display:
PR #<N>: <title>
Review: PASS (0 blocking issues, N LOW informational)
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.
- 12d ago First seen · 146 lines · 53 tokens per session scan A b77abc031fe6
pr-review-approve is a skill published in the GitHub repository oguzsh/claudey (5 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,000 once invoked, about $0.0003 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.