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/boshu2/agentopsWrote 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/boshu2/agentops/code-reviewer)<a href="https://agentmods.dev/agents/boshu2/agentops/code-reviewer"><img src="https://agentmods.dev/badge/agents/boshu2/agentops/code-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/boshu2/agentops/code-reviewer"><img src="https://agentmods.dev/badge/agents/boshu2/agentops/code-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.00026 | $0.00159 |
| Opus 5.5 | $0.00010 | $0.00064 |
| Sonnet 5.5 | $0.00005 | $0.00032 |
| Haiku 4.5 | $0.00003 | $0.00016 |
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 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.
What it actually says
You are a senior code reviewer. When invoked:
- Run
git diffto see recent changes - Focus on modified files
- Review for quality, security, and maintainability
Provide feedback organized by priority:
- Critical (must fix): Security vulnerabilities, data loss risks, broken functionality
- Warning (should fix): Performance issues, error handling gaps, test coverage
- Suggestion (consider): Readability improvements, naming conventions, documentation
Include specific code references and examples of how to fix 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.
- 1mo ago First seen · 20 lines · 26 tokens per session scan A 4a1264612d30
code-reviewer is an agent published in the GitHub repository boshu2/agentops (449 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 159 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
spring-boot-reviewer
Reviews Spring Boot codebases against all spring-boot skills for correctness, best practices, and Spring Boot 4 compatibility. Use when reviewing Spring Boot projects, validating implementations, or user mentions "review my Spring Boot code", "check Spring best practices", "Spring Boot review", "validate Spring…
pragmatic-code-review
Single-pass code reviewer for delegation by other workflows. Use when another agent or workflow needs to spawn a focused code review as a subtask. For full multi-agent orchestrated reviews, use /review:code-review instead.
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
code-reviewer
Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication…
audit-design
Audits plugin design quality — over-engineering, hook quality, and architectural patterns. Dispatched by /hone during Phase 2.
code-reviewer
Implementation-review role for the tdd-pipeline plugin. Reads code written by the implementer agent, checks correctness, resource management, and quality, and reports findings. Does not write code. Dispatched by tdd-orchestrate; not for direct user invocation.