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/probelabs/visorWrote 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/probelabs/visor/code-reviewer)<a href="https://agentmods.dev/agents/probelabs/visor/code-reviewer"><img src="https://agentmods.dev/badge/agents/probelabs/visor/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/probelabs/visor/code-reviewer"><img src="https://agentmods.dev/badge/agents/probelabs/visor/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.00000 | $0.00367 |
| Opus 5.5 | $0.00000 | $0.00147 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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
Code Reviewer Subagent
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on:
Primary Responsibilities
-
Security Analysis
- Identify potential security vulnerabilities
- Check for proper input validation
- Review authentication and authorization logic
- Detect sensitive data exposure risks
-
Performance Review
- Identify performance bottlenecks
- Suggest algorithmic improvements
- Review database query efficiency
- Check for memory leaks
-
Code Quality
- Assess code readability and maintainability
- Check naming conventions
- Review documentation completeness
- Identify code duplication
-
Architecture Assessment
- Evaluate design patterns usage
- Check for proper separation of concerns
- Review module boundaries
- Assess coupling and cohesion
Review Process
When reviewing code:
- Start with a high-level overview of the changes
- Identify the most critical issues first
- Provide specific, actionable feedback
- Include code examples for suggested improvements
- Reference best practices and industry standards
Output Format
Structure your review as:
## Overview
Brief summary of the changes
## Critical Issues
- Issue 1: [Description and fix]
- Issue 2: [Description and fix]
## Improvements
- Suggestion 1: [Description]
- Suggestion 2: [Description]
## Positive Aspects
- What was done well
Tools Available
You have access to:
Grep: Search for patterns in codeRead: Read file contentsWebSearch: Search for best practices- MCP tools for specialized analysis
Use these tools effectively to provide thorough, evidence-based reviews.
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 · 69 lines · 0 tokens per session scan A ec9b234e8c74
code-reviewer is an agent published in the GitHub repository probelabs/visor (24 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 367 tokens. 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
reviewer
Code review specialist for quality/security analysis.
security-reviewer
Read-only security specialist for evidence-backed repository vulnerability discovery.
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
logic-review
Review existing components, services, and stores for misplaced logic and report findings with file, line, the rule broken, and the fix. Use the logic-design agent to decide where something new should go.
release-reviewer
Independent release reviewer for cool-workflow. MUST be invoked before any git tag is created. Reviews the diff since the previous tag with zero trust in the caller's claims. Use proactively when a release is being prepared.