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/cofin/flowWrote 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/cofin/flow/code-reviewer)<a href="https://agentmods.dev/agents/cofin/flow/code-reviewer"><img src="https://agentmods.dev/badge/agents/cofin/flow/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/cofin/flow/code-reviewer"><img src="https://agentmods.dev/badge/agents/cofin/flow/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.00022 | $0.00334 |
| Opus 5.5 | $0.00009 | $0.00134 |
| Sonnet 5.5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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
{
"canonical_id": "code-reviewer",
"canonical_source": "agents/code-reviewer.md",
"git_tags": "forbidden",
"host": "vscode_copilot",
"instruction": "Read and follow the canonical agent source directly.",
"interaction_requirement": "none",
"invariant_ids": [
"review-findings-v1",
"git-no-tags-v1"
],
"kind": "flow_agent_adapter",
"question_capability": {
"bounds_enforcement": "unsupported",
"choice_max": null,
"choice_min": null,
"custom_answer_behavior": "sequential_text_only",
"disabled_choice_policy": "omit",
"evidence": "No verified Flow-native VS Code Copilot question tool",
"multi_select": false,
"mutual_exclusion": false,
"permission_check": "not_applicable",
"sequential_fallback": true,
"supported_modes": [],
"tool": null,
"transport": "sequential_text"
},
"tool_capability_requirements": [
"file_read",
"repository_diff"
]
}
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 · 42 lines · 22 tokens per session scan A 9b6920b2f3f0
code-reviewer is an agent published in the GitHub repository cofin/flow (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 334 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
principal-engineer
Senior principal engineer for complex architectural decisions, debugging after 2+ failed attempts, unfamiliar patterns, security-critical code review, and high-stakes technical decisions.
security-engineer
Application security review for OWASP Top 10 and CVE analysis. Use after code changes, dependency updates, or for pre-release security checks. Focuses on recently written code, not full codebase audits.
typescript-reviewer
Expert TypeScript code reviewer specializing in type safety, async correctness, security, and idiomatic patterns.
golang-reviewer
Expert Go code reviewer specializing in error handling, concurrency safety, interface design, and idiomatic patterns.
lua-reviewer
Expert Lua code reviewer specializing in Neovim plugin quality, metatable correctness, performance patterns, and API usage.
nix-reviewer
Expert Nix code reviewer specializing in reproducibility, flake hygiene, NixOS module design, and security.