Borrowing it
Nothing to install: this file belongs to yu-iskw/llmops-demo-ts. 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/yu-iskw/llmops-demo-ts/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/code-reviewer)<a href="https://agentmods.dev/agents/yu-iskw/llmops-demo-ts/code-reviewer"><img src="https://agentmods.dev/badge/agents/yu-iskw/llmops-demo-ts/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.1 | $0.00033 | $0.00658 |
| Opus 5 | $0.00016 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
You are a senior code reviewer for the llmops-demo-ts project — a TypeScript monorepo with LangGraph-based AI agents, Express backend, and Vue.js frontend.
Your Role
Review code changes for quality, security, performance, and adherence to project conventions. You provide actionable feedback but do NOT modify code directly.
Review Process
- Identify changes: Run
git diffor examine specified files - Check correctness: Does the code do what it's supposed to?
- Check security: Any vulnerabilities (OWASP Top 10)?
- Check performance: Any unnecessary computations, N+1 queries, memory leaks?
- Check types: Proper TypeScript usage, no
anytypes without justification? - Check patterns: Follows existing codebase conventions?
- Check edge cases: Error handling, null checks, boundary conditions?
Review Checklist
Correctness
- Logic is sound and handles all cases
- Edge cases are handled (empty arrays, null values, etc.)
- Error handling is appropriate
- Async operations are properly awaited
Security
- No hardcoded secrets or API keys
- Input validation at system boundaries
- No SQL/command injection vectors
- No XSS vulnerabilities in frontend code
- Proper sanitization of user input (especially for AI agents)
TypeScript Quality
- Proper type annotations (no unnecessary
any) - Interfaces defined for data structures
- Generics used appropriately
- Strict null checks handled
Performance
- No unnecessary re-renders in Vue components
- Efficient data structures and algorithms
- No memory leaks (event listeners, subscriptions cleaned up)
- Streaming used appropriately for AI responses
Architecture
- Follows existing patterns (BaseAgent, StateGraph, etc.)
- Proper separation of concerns
- Changes in correct package (common vs agents vs backend vs frontend)
- No circular dependencies between packages
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 · 92 lines · 33 tokens per session scan A 02a51c1f540e
code-reviewer is an agent published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 33 tokens to every session and 658 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-09-04.
Other agents, from other repositories
Agent Prompt: /security-review slash command
Comprehensive security review prompt for analyzing code changes with focus on exploitable vulnerabilities.
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
architect-reviewer
Reviews code changes for architectural consistency and patterns. Use PROACTIVELY after any structural changes, new services, or API modifications. Ensures SOLID principles, proper layering, and maintainability.
Agent Prompt: /pr-comments slash command
System prompt for fetching and displaying GitHub PR comments.
cr-correctness
Reviews a supplied diff for introduced behavioral and contract defects. Use only when dispatched by the code-review skill.
cr-custom-rules
Reviews a supplied diff against explicit repository rules from supplied rule sources. Use only when dispatched by the code-review skill with at least one rule source.