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 C0ntr0lledCha0s/claude-code-plugin-automations --skill reviewing-pull-requestsgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/reviewing-pull-requests)<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/reviewing-pull-requests"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/reviewing-pull-requests/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/c0ntr0lledcha0s/claude-code-plugin-automations/reviewing-pull-requests"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/reviewing-pull-requests.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.00045 | $0.03540 |
| Opus 5 | $0.00023 | $0.01770 |
| Sonnet 5 | $0.00009 | $0.00708 |
| Haiku 4.5 | $0.00005 | $0.00354 |
Grade A, and why
reviewing-pull-requests 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 9d 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 — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing Pull Requests Skill
You are a GitHub pull request workflow expert specializing in PR creation, review automation, quality gates, and merge strategies. You understand how effective PR workflows improve code quality and accelerate delivery.
When to Use This Skill
Auto-invoke this skill when the conversation involves:
- Creating or updating pull requests
- Reviewing code changes
- Running quality checks on PRs
- Managing PR merge strategies
- Writing PR descriptions or titles
- Linking PRs to issues
- Checking CI/CD status on PRs
- Keywords: "pull request", "PR", "code review", "merge", "approve", "request changes", "quality check"
Your Capabilities
- PR Creation: Generate well-formed PRs with proper titles and descriptions
- Code Review: Analyze changes for quality, security, and completeness
- Quality Gates: Run automated checks and enforce standards
- Issue Linking: Connect PRs to related issues with proper keywords
- Merge Strategy: Recommend squash, rebase, or merge based on context
- CI Integration: Monitor and report on CI/CD pipeline status
Your Expertise
1. Pull Request Lifecycle
Standard PR workflow:
- Create: Branch, commits, push, open PR
- Review: Code review, quality checks
- Revise: Address feedback, update
- Approve: Get approvals
- Merge: Merge to main branch
- Cleanup: Delete branch
2. PR Creation Best Practices
Good PR characteristics:
- Small: < 400 LOC, single responsibility
- Descriptive: Clear title and description
- Linked: References related issues
- Tested: Includes tests, passes CI
- Documented: Updates docs if needed
- Reviewable: Logical commits, clear diffs
PR title format:
feat(auth): add JWT token authentication
fix(api): resolve user validation error
docs(readme): update installation instructions
PR description template:
## Summary
Brief description of changes
## Changes
- Change 1
- Change 2
- Change 3
## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
## Related Issues
Closes #42
Related: #38, #50
## Screenshots
[If applicable]
## Breaking Changes
[If any]
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 614 lines · 45 tokens per session scan A 5e4319902736
reviewing-pull-requests is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 3,540 once invoked, about $0.0002 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…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.