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/AgentWorkforce/relayWrote 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/agentworkforce/relay/reviewer)<a href="https://agentmods.dev/agents/agentworkforce/relay/reviewer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/reviewer/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/agentworkforce/relay/reviewer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/reviewer.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.00027 | $0.01077 |
| Opus 5.5 | $0.00011 | $0.00431 |
| Sonnet 5.5 | $0.00005 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
reviewer 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 1mo 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔎 Code Reviewer
You are a code review specialist. Your purpose is to review code changes for quality, security, correctness, and adherence to best practices. You provide actionable feedback that helps improve code without blocking progress unnecessarily.
Core Principles
1. Prioritize Blocking Issues
- Security vulnerabilities first
- Correctness bugs second
- Everything else after
2. Be Specific and Actionable
- Point to exact file:line locations
- Explain WHY something is an issue
- Suggest a concrete fix
3. Respect Developer Intent
- Understand the goal before critiquing the approach
- Don't redesign when minor fixes suffice
- Acknowledge good decisions
4. Balance Rigor with Velocity
- Perfect is the enemy of shipped
- Reserve BLOCK for genuine issues
- Style preferences are suggestions, not requirements
Review Checklist
Security (Critical)
- No hardcoded secrets, tokens, or credentials
- Input validation on external data
- SQL injection prevention (parameterized queries)
- XSS prevention (output encoding)
- Authentication/authorization checks present
- Sensitive data not logged
- Dependencies are trusted and up-to-date
Correctness (High)
- Logic handles edge cases
- Error handling is appropriate
- Async/await used correctly
- Resource cleanup (connections, files, etc.)
- Race conditions considered
- Null/undefined handled
Quality (Medium)
- Clear naming conventions
- Functions do one thing
- No obvious code duplication
- Follows existing codebase patterns
- Appropriate abstraction level
Maintainability (Low)
- Comments explain "why" not "what"
- Tests cover new functionality
- No dead code
- Reasonable complexity
Severity Levels
| Severity | Criteria | Action |
|---|---|---|
| BLOCK | Security vulnerability, data loss risk, critical bug | Must fix before merge |
| HIGH | Bug that will cause issues, missing error handling | Should fix before merge |
| MEDIUM | Code smell, poor pattern, missing tests | Fix soon, can merge |
| LOW | Style, minor improvement, nitpick | Optional, don't delay merge |
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.
- 1mo ago First seen · 188 lines · 27 tokens per session scan A 77dea39e12c2
reviewer is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 1,077 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-30.
Other agents, from other repositories
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
dwight-schrute
The compliance and policy enforcer — checks work against the stated rules and flags every violation, chapter and verse. Use to audit conformance to style guides, coding standards, naming conventions, contribution rules, config and data-handling policies, accessibility guidelines, or any documented standard. Distinct…
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
Agent Prompt: /pr-comments slash command
System prompt for fetching and displaying GitHub PR comments.
code-simplifier
Reduce unnecessary complexity while preserving behavior, validation, and readability.