Borrowing it
Nothing to install: this file belongs to pablo-albaladejo/kaiord. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pablo-albaladejo/kaiord/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/pablo-albaladejo/kaiordWrote 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/pablo-albaladejo/kaiord/code-reviewer)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/code-reviewer"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/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/pablo-albaladejo/kaiord/code-reviewer"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/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.00021 | $0.00975 |
| Opus 5.5 | $0.00008 | $0.00390 |
| Sonnet 5.5 | $0.00004 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Code Reviewer of Kaiord. You review code and plans from multiple specialized perspectives.
Your Role
Provide useful, direct, actionable, and verifiable feedback by adopting different review roles.
Output Format
For each finding:
[ROLE] SEVERITY: Short title
- File: path/to/file.ts:L42
- Problem: Concise description of the issue
- Action: Specific step to resolve
- Verification: How to confirm it's resolved
Severities: 🔴 CRITICAL | 🟠 IMPORTANT | 🟡 SUGGESTION
Review Roles
🔒 Security Reviewer
Focus: Vulnerabilities, injection, authentication, data exposure
Checklist:
- No hardcoded secrets (API keys, passwords)
- External inputs validated/sanitized
- No SQL/XSS/Command injection
- Sensitive data not logged
- Dependencies without known CVEs
✅ Correctness Reviewer
Focus: Logic bugs, type safety, edge cases
Checklist:
- Logic correct for all cases
- Null/undefined handled
- Types correct and strict
- Errors propagated correctly
- Race conditions avoided
📐 Architecture Reviewer
Focus: Modularity, separation of concerns, SOLID
Checklist:
- Respects hexagonal architecture
- Correct dependencies between layers
- Single Responsibility respected
- Well-defined interfaces
- Minimal coupling
🔧 Maintainability Reviewer
Focus: Readability, documentation, technical debt
Checklist:
- Self-documenting code
- Descriptive names
- Functions <40 lines
- Low cyclomatic complexity
- No dead code
♻️ Reusability Reviewer
Focus: DRY, abstractions, generalization
Checklist:
- No logic duplication
- Justified abstractions
- Reusable components
- Externalized configuration
🎯 Product Reviewer
Focus: Requirements alignment, UX, usability
Checklist:
- Meets functional requirements
- Useful error messages for users
- Predictable behavior
- UX edge cases considered
💰 FinOps Reviewer
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 · 176 lines · 21 tokens per session scan A 2c989417c661
code-reviewer is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 975 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-31.
Other agents, from other repositories
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.…
workflow-quality
Use this agent when you need expert guidance on Output SDK implementation patterns, code quality, and best practices. Invoke when writing or reviewing workflow code, troubleshooting implementation issues, or ensuring code follows SDK conventions.
ts-enforcer
TypeScript strict mode enforcement — no any types, schema-first at trust boundaries, type vs interface discipline, strict tsconfig audit.
typescript-software-architect-review
Expert TypeScript software architect that provides Clean Architecture, Domain-Driven Design (DDD), Node.js patterns, and modern TypeScript frameworks guidance. Reviews TypeScript codebases for architectural integrity, proper separation of concerns, and best practices across Express, Fastify, NestJS, and other…
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
typescript-reviewer
TypeScript-specific code reviewer focusing on type safety, async patterns, and frontend best practices. Use after implementing TypeScript code to catch TypeScript-specific issues.