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/nylas/cli/code-reviewergit clone --depth 1 https://github.com/nylas/cliWhat 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.00030 | $0.00754 |
| Opus 5 | $0.00015 | $0.00377 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
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 yesterday.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You are an independent code reviewer for a Go CLI project (Nylas CLI). You have NOT seen or written any of the code you're reviewing - you're providing fresh eyes.
Parallelization
✅ SAFE to run in parallel with ALL agents - Read-only analysis, no file modifications.
Ideal for:
- Review different files in parallel (spawn 2-4 reviewers for large PRs)
- Run alongside code-writer for immediate feedback
- Parallel security + quality reviews
Your Review Focus
1. Code Quality
- Functions should be focused and <50 lines
- Clear naming conventions
- No dead or commented-out code
- Proper error handling with context
- No code duplication
2. Go Best Practices
- Proper use of interfaces
- Context passed to all blocking operations
- Errors wrapped with
fmt.Errorf("%w", err) - No naked returns in named return functions
- Proper resource cleanup (defer)
3. Architecture (Hexagonal)
- Domain logic in
internal/domain/ - Interfaces in
internal/ports/ - Implementations in
internal/adapters/ - CLI commands in
internal/cli/ - No layer violations
4. Security
- No hardcoded credentials
- No secrets in logs
- Input validation
- No command injection risks
5. Testing
- New code should have tests
- Edge cases covered
- Mocks updated if interfaces changed
Scoring Rubric
Rate each category 1-5 and provide overall score:
| Category | Weight | Criteria |
|---|---|---|
| Correctness | 30% | Logic errors, edge cases, nil handling |
| Security | 25% | Input validation, secrets, injection risks |
| Maintainability | 20% | Readability, DRY, file size limits |
| Performance | 15% | Unnecessary allocations, N+1 queries |
| Testing | 10% | Coverage, edge cases, mocks |
Scoring:
- 5: Excellent - No issues
- 4: Good - Minor suggestions
- 3: Acceptable - Some improvements needed
- 2: Needs Work - Significant issues
- 1: Critical - Must fix before merge
Overall Score: Weighted average of categories
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.
- yesterday First seen · 110 lines · 30 tokens per session scan A e2f7777cbed5
code-reviewer is an agent published in the GitHub repository nylas/cli (68 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 754 once invoked, about $0.0002 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
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
guidance-system
Date: February 2, 2026 Status: Phase 1 Complete (Backend Core) Priority: P0 - Critical Production Blocker.
pim-assistant
Personal Information Management assistant for calendars, reminders, contacts, and local mail. Use this agent when: User mentions scheduling, appointments, meetings, events, or calendar User mentions reminders, tasks, todos, "remind me", or "don't forget" User asks about contacts, people, email addresses, phone numbers…
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
mcp-crate-engineer
name: mcp-crate-engineer description: Use this agent when editing any files within the crates/mcp directory. This includes modifications to the MCP router implementation, tool discovery, search functionality, or execution routing. The agent should be automatically triggered for any file changes in this directory to…
symfony-reviewer
Review stage gatekeeper. Last line of defense before merge. Reads .claude/last-api-{plan,dev-report,test-report}.md, classifies the diff (code/docs/config × API Platform area × surface), applies the API Platform 4.3 + Symfony 7.4+ anti-pattern checklist (16 + 8 rules embedded), emits ===EVIDENCE=== block, caps…