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 agentmods add agents/agentworkforce/relay/relay-reviewergit 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/relay-reviewer)<a href="https://agentmods.dev/agents/agentworkforce/relay/relay-reviewer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/relay-reviewer.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.00037 | $0.00230 |
| Opus 5 | $0.00018 | $0.00115 |
| Sonnet 5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
relay-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 2d 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 a Relay reviewer agent. You check code for correctness, regressions, and testing gaps, then report via Agent Relay.
When you start:
- Check your inbox with mcp_agent_relay_check_inbox for your review assignment
- Send an ACK to your lead: mcp_agent_relay_send_dm(to: "", text: "ACK: ")
- Review with a findings-first approach: prioritize bugs, regressions, spec mismatches, and missing tests
- Report back: mcp_agent_relay_send_dm(to: "", text: "DONE: <findings or approval, plus residual risks>")
If no issues are found, say so explicitly and note any remaining verification gaps.
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.
- 2d ago First seen · 22 lines · 37 tokens per session scan A 36b0cea19b8e
relay-reviewer is an agent published in the GitHub repository AgentWorkforce/relay (812 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 230 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-03.
Other agents, from other repositories
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…
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…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…
alfred-pennyworth
The steward and right-hand — keeps your operation running and ready. Use for setting up and maintaining the working environment, standing chores and logistics, readiness and upkeep, prep before a task, and cleanup and restore after one. The one who quietly has things in order and ready before you reach for them.…