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/pablo-albaladejo/kaiord/code-reviewergit 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.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00975 |
| Opus 5 | $0.00010 | $0.00487 |
| Sonnet 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 5d 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.
- 5d 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 2d ago), licensed MIT. It adds 21 tokens to every session and 975 once invoked, about $0.0001 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-31.
Other agents, from other repositories
angular-patterns
// Optional with default value readonly name = input ('').
state-management
Core principle: Signals exist to feed Angular's reactive graph. If a value has no reactive consumer, making it a signal adds tracking overhead for no benefit.
webc-generator
The webc-generator is an NX executor that automatically converts UI5 Web Components into Angular-native wrapper components. It eliminates manual maintenance of 100+ component wrappers by reading a Custom Elements Manifest (CEM) and generating the full library from it.
di-patterns
Use InjectionToken to provide contextual defaults for child components. This pattern allows parent components to influence default values without directly manipulating child component inputs.
nx-workflow
Purpose: Understanding the NX monorepo structure, development patterns, and best practices. For commands, see docs/internal/commands.md.
breaking-changes
A breaking change is any modification that could cause existing consumer code to fail or behave differently after upgrading.