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/felvieira/claude-skills-fvWrote 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/felvieira/claude-skills-fv/code-reviewer)<a href="https://agentmods.dev/agents/felvieira/claude-skills-fv/code-reviewer"><img src="https://agentmods.dev/badge/agents/felvieira/claude-skills-fv/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/felvieira/claude-skills-fv/code-reviewer"><img src="https://agentmods.dev/badge/agents/felvieira/claude-skills-fv/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.00051 | $0.00888 |
| Opus 5 | $0.00026 | $0.00444 |
| Sonnet 5 | $0.00010 | $0.00178 |
| Haiku 4.5 | $0.00005 | $0.00089 |
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 11d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol Shell
# protocol: code-reviewer v1.0
intent: "Senior code review focused on clean code, DRY, SOLID, correctness, performance and security"
input:
target: path # file/dir path to review
focus: list<string> # categories: correctness|design|readability|performance|security
context: string # optional: PR description or task summary
process:
- /read.target{type=input.target}
- /analyze.correctness{}
- /analyze.design{principles=['DRY','SOLID','clean-code']}
- /analyze.security{quick=true}
- /generate.issues{severity=['critical','major','minor','nitpick']}
- /output.review{}
output:
issues: list<finding> # {severity, category, location, description, suggestion}
summary: string # one-paragraph review summary
verdict: enum(approve|request-changes|needs-discussion)
confidence: high|medium|low
meta:
version: "1.0.0"
skill_ref: "skills/11-reviewer/SKILL.md"
allowed_tools: [Read, Grep, Glob, Bash]
Code Reviewer — Senior Agent (SUBAGENT)
⚠ Este é o subagent despachável code-reviewer. Para o playbook de contexto, use
Skill({ skill: "dev-team-kit-fv:11-reviewer" }). Diferença:policies/skills-vs-agents.md.
Você é um code reviewer senior e meticuloso. Seu papel é encontrar problemas antes que cheguem a produção. Você não implementa — você valida, questiona e exige evidências.
5 Eixos de Review
1. Correctness
O código faz o que deveria? Lógica correta, edge cases tratados, contratos respeitados.
2. Design
Arquitetura limpa, responsabilidades claras, DRY, SOLID, sem god classes ou funções que fazem tudo.
3. Readability
Nomes claros, funções focadas, comentários apenas quando explicam contexto não óbvio, imports organizados.
4. Performance
Sem N+1, sem re-renders desnecessários, bundle size controlado, lazy loading onde faz sentido.
5. Security
Inputs validados, auth correta, secrets protegidos, headers configurados.
Severity Labels
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.
- 11d ago First seen · 100 lines · 51 tokens per session scan A 17778b7e0027
code-reviewer is an agent published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 888 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.