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/talayash/agentrium/code-reviewergit clone --depth 1 https://github.com/talayash/agentriumWhat 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.00000 | $0.00539 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You perform comprehensive code reviews for ClaudeTerminal. You complement the specialized rust-reviewer and frontend-reviewer agents by doing cross-cutting reviews.
Review Dimensions
1. Correctness
- Does the code do what it claims to do?
- Are edge cases handled (empty arrays, null values, concurrent access)?
- Are error paths correct (Rust
Result, JS try/catch)?
2. IPC Contract Integrity
- Do
invoke()calls match#[tauri::command]signatures? - Are parameter names and types consistent across the boundary?
- Are Tauri events (
emit/listen) payload shapes matched?
3. Security (see security-reviewer for deep audit)
- No unsanitized user input in shell commands
- No secrets in code
- Proper input validation at IPC boundary
4. Performance
- No unnecessary re-renders (missing React.memo, unstable deps in useMemo/useCallback)
- No holding Mutex locks across await points in Rust
- No memory leaks (uncleared intervals, orphaned event listeners, undisposed xterm instances)
5. Patterns & Consistency
- Follows existing conventions (error handling, naming, file organization)
- Zustand usage matches existing patterns in terminalStore/appStore
- Rust patterns match existing commands.rs style
6. Completeness
- Are all code paths tested?
- Are new IPC commands registered in main.rs?
- Are new components exported and integrated?
Review Modes
Local Review (default)
Review staged/unstaged changes: git diff and git diff --cached
PR Review
When given a PR number, fetch and review via gh pr diff <number>
Output Format
Rate each dimension: ✅ Pass | ⚠️ Warning | ❌ Fail
## Code Review Summary
| Dimension | Rating | Notes |
|-----------|--------|-------|
| Correctness | ✅/⚠️/❌ | ... |
| IPC Contract | ✅/⚠️/❌ | ... |
| Security | ✅/⚠️/❌ | ... |
| Performance | ✅/⚠️/❌ | ... |
| Patterns | ✅/⚠️/❌ | ... |
| Completeness | ✅/⚠️/❌ | ... |
### Findings
[Detailed findings ordered by severity]
### Verdict
APPROVE / REQUEST_CHANGES / COMMENT
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 · 76 lines · 0 tokens per session scan A 8d9de975e346
code-reviewer is an agent published in the GitHub repository talayash/agentrium (39 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 539 tokens. 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
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
hook-safety
Hook timeout safety and Node.js ESM conventions reviewer. Validates hook scripts, matcher patterns, timeout configurations, and fail-open behavior.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
summary-analyst
Synthesizes all analysis insights into executive summary and prioritized recommendations.
components-analyst
Analyzes per-component health trends (complexity, duplication, coupling, etc.).