Borrowing it
Nothing to install: this file belongs to teabranch/open-responses-server. 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/teabranch/open-responses-server/main/.claude/skills/pr-review/SKILL.mdgit clone --depth 1 https://github.com/teabranch/open-responses-serverWrote 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/teabranch/open-responses-server/pr-review)<a href="https://agentmods.dev/skills/teabranch/open-responses-server/pr-review"><img src="https://agentmods.dev/badge/skills/teabranch/open-responses-server/pr-review.svg" alt="Measured on agentmods" 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.00071 | $0.01470 |
| Opus 5 | $0.00036 | $0.00735 |
| Sonnet 5 | $0.00014 | $0.00294 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
pr-review 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 8d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Workflow
Complete pull request lifecycle for the open-responses-server project. Follow every step in order.
Step 1 — Branch
If you are on main, create a feature branch first:
git checkout -b <branch-name>
Branch naming conventions:
| Type | Pattern | Example |
|---|---|---|
| Bug fix | fix/<short-desc> |
fix/streaming-error-handling |
| Feature | feat/<short-desc> |
feat/persistent-history |
| Docs | docs/<short-desc> |
docs/event-system-refresh |
Step 1b — Check for existing PRs on the branch
Before adding new work to an existing branch, check if there's already an open PR:
gh pr view --json number,title,state --jq '{number,title,state}'
If the command fails with "no pull requests found", there is no open PR —
proceed normally. Only act on the result if it returns valid JSON with
state: "OPEN".
If an open PR exists and your new changes are unrelated to that PR's scope, stop and ask the user:
"There's an open PR (#N: 'title') on this branch. The new changes are unrelated to that PR. Would you like to merge the existing PR first before starting the new work?"
Wait for the user's answer before proceeding.
Step 2 — Make changes, commit, push
-
Edit code
-
Run tests:
python -m pytest tests/ -v -
Run lint:
flake8 src/ -
Stage and commit:
git add <files> git commit -m "$(cat <<'EOF' Commit message here. Co-Authored-By: Claude Opus 4.6 <[email protected]> EOF )" -
Push:
git push -u origin <branch-name>
Step 3 — Create PR
gh pr create --title "Short title" --body "$(cat <<'EOF'
## Summary
- Bullet points describing changes
## Test plan
- [ ] Test items
- Claude
EOF
)"
Step 4 — Wait for reviewers
Automated reviewers (Qodo, Copilot) need time to post comments.
Wait 5 minutes after creating the PR before checking for comments:
sleep 300
Step 5 — Poll for comments
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.
- 8d ago First seen · 210 lines · 71 tokens per session scan A 4223d79ee237
pr-review is a skill published in the GitHub repository teabranch/open-responses-server (185 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,470 once invoked, about $0.0004 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-30.
Other skills, from other repositories
archestra-pr-hygiene
Use when opening or updating an Archestra pull request to write an accurate conventional title and a practical, evidence-based description.
code-review
A code-review and quality-analysis skill written in Chinese. It is intended to inspect code, find potential problems, and suggest improvements.
git-github-workflow
A guide for collaborating on code with Git and GitHub. Git tracks changes locally, while GitHub hosts repositories and supports pull requests, reviews, and team workflows.
pr-analysis
Analyse a GitHub pull request by fetching its metadata, diff, linked issues and CI status.
review
Role: Staff Engineer Inputs: current git diff (uncommitted or branch-diff) Outputs: review-report.md Next skill: /ship Audit actions: review.started, review.findingsrecorded, review.completed.
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.