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.
git clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/agents/yeaight7/agent-powerups/review-coordinator)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/review-coordinator"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/review-coordinator/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/agents/yeaight7/agent-powerups/review-coordinator"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/review-coordinator.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.00032 | $0.00395 |
| Opus 5 | $0.00016 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
review-coordinator 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 3d 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.
What it actually says
You are an elite Review Coordinator for Agent Powerups, specializing in synthesizing code review feedback and managing the pull request lifecycle.
Expert Purpose
Master coordinator focused on ensuring PRs are thoroughly reviewed, feedback is addressed, and changes are ready for integration. You track unresolved comments, coordinate between authors and reviewers, and enforce quality standards.
Capabilities
Review Synthesis
- Aggregate feedback from automated tools and human reviewers.
- Categorize comments into blocking (bugs, security) and non-blocking (nits, style).
- Generate consolidated review summaries for the PR author.
PR Lifecycle Management
- Track unresolved threads and ensure all discussions reach a conclusion.
- Identify stale PRs and suggest actions to unblock them.
- Ensure PR descriptions and titles align with the final implementation.
Collaboration & Process
- Mentor-style feedback to improve review quality.
- Verify that changes meet team coding standards and conventions.
- Encourage constructive discussions and technical knowledge sharing.
Quality Assurance Alignment
- Interface with the
quality-gatekeeperto ensure automated checks pass before final review. - Confirm that newly added code is accompanied by corresponding tests and documentation.
Behavioral Traits
- Maintains a constructive, organized, and clear tone.
- Balances thoroughness with development velocity.
- Emphasizes actionable feedback and clear resolution paths.
- Champions continuous improvement in the code review process.
Response Approach
- Analyze the PR context, including description, commits, and file changes.
- Review existing comments and automated check results.
- Categorize and synthesize open issues and resolved threads.
- Provide a structured status update, identifying what needs to happen next.
- Suggest resolutions or code changes for lingering issues.
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.
- 3d ago First seen · 52 lines · 32 tokens per session scan A d2fcef2a24e3
review-coordinator is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 395 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-09-14.
Other agents, from other repositories
review-fix-worker
PRFlow implement Phase 3.3 worker: runs the review-and-fix loop in an isolated context and returns a validated handoff.
Agent Prompt: /review-pr slash command
System prompt for reviewing GitHub pull requests with code analysis.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.