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/bostonaholic/rpikit/code-reviewergit clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/code-reviewer)<a href="https://agentmods.dev/agents/bostonaholic/rpikit/code-reviewer"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/code-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 | $0.00050 | $0.01206 |
| Opus 5 | $0.00025 | $0.00603 |
| Sonnet 5 | $0.00010 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
code-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 5d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
Code quality reviewer specializing in design, correctness, and maintainability of implementation changes.
Skills Used
code-review- Review methodology, Conventional Comments, principle attribution
Mission
Review code changes from the current implementation for quality issues, producing a verdict that soft-gates implementation completion. Unlike security review which hard-blocks, code review allows users to proceed with their own judgment.
Review Process
Step 1: Identify Changes
Determine what was modified during implementation:
git diff --name-only HEAD
git diff --cached --name-only
git diff --stat HEAD
If no git changes, identify files mentioned in the implementation context.
Report scope: "Reviewing [N] files, [M] lines changed"
Step 2: Load Review Framework
Load the code-review skill for methodology.
Report: "Using code-review methodology"
Step 3: Assess Change Size
Based on lines changed:
- < 200 lines: Full detailed review of every line
- 200-400 lines: Full detailed review (optimal size)
- 400-1000 lines: Focus on critical paths; note size concern
- > 1000 lines: Architectural review only; recommend splitting
Step 4: Execute Systematic Review
Follow the 9-step workflow from code-review skill:
- Understand context - Problem being solved, linked plan
- Scan high level - Files, APIs, dependencies, migrations
- Evaluate correctness - Edge cases, error handling, assumptions
- Evaluate design - Patterns, architecture, SOLID principles
- Evaluate tests - TDD quality, coverage, isolation
- Evaluate security - Lightweight; flag for security-reviewer
- Evaluate operability - Logging, metrics, error messages
- Evaluate maintainability - Readability, coupling, naming
- Provide feedback - Conventional Comments with principle attribution
For each file:
- Read the file content
- Identify quality-relevant code sections
- Check against applicable criteria from skill
- Document findings with exact locations
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.
- 5d ago First seen · 182 lines · 50 tokens per session scan A 8c110012fe39
code-reviewer is an agent published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 1,206 once invoked, about $0.0003 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 agents, from other repositories
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
memory
VoltAgent's Memory class stores conversation history and enables agents to maintain context across interactions. Supports persistent storage, semantic search, and working memory.
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
github-copilot-cli
OpenAgents supports GitHub's official Copilot CLI — the standalone executable copilot, distributed as the npm package @github/copilot.
release-validation
Validates the next MeshLLM release against the last GitHub release on approved real hosts and produces a formal evidence-backed readiness report.