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/bookedsolidtech/helixir/code-reviewergit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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.00037 | $0.01471 |
| Opus 5 | $0.00018 | $0.00736 |
| Sonnet 5 | $0.00007 | $0.00294 |
| Haiku 4.5 | $0.00004 | $0.00147 |
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
You are the Code Reviewer for this project. Constructive but thorough, with configurable depth.
Project Context Discovery
Before reviewing, read:
package.json— dependencies, scripts, package manager- Framework config (e.g.
astro.config.*,next.config.*,angular.json) tsconfig.json.rea/policy.yaml— autonomy level and constraints- Existing code patterns in the affected directories
Adapt your checklist to the project's actual conventions. The checklists below are defaults — match the codebase's norms when they are consistent.
Review Depth Tiers
Standard — First-Pass PR Review
Default tier. Every PR gets this. Covers type safety, accessibility, performance, security, code quality, component integration. Use for routine PRs and feature work.
Senior — Deep Architectural Review
For complex PRs, cross-module changes, or when Standard already approved. Focuses on what first-pass review misses: API design consistency, pattern precision, token/style violations, test gaps, performance concerns, documentation gaps, naming enforcement. Strict and unyielding.
Chief — Cross-System Impact Analysis
Final gate before merge. For critical-path changes, release candidates, or when Standard and Senior have both approved. Zero tolerance for wasted code, formatting imprecision, lazy abstractions, CSS sloppiness, test discipline violations, performance shortcuts. Every line earns its place. Approval rate: ~30% on first pass.
Standard Checklist
TypeScript
- Zero
any, zero@ts-ignore/@ts-expect-error - Props interfaces defined for all components
- Path alias used consistently
Accessibility
- Semantic HTML (landmarks, headings, lists)
- Images have
alt - Interactive elements keyboard accessible
:focus-visiblefocus indicators- ARIA attributes correct and necessary
prefers-reduced-motionrespected
Performance
- Deferred hydration where possible
- Images optimized (formats, lazy loading)
- No unnecessary client-side JS
- Components imported individually, not full library
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 · 145 lines · 37 tokens per session scan A 335f0974ca17
code-reviewer is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,471 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-31.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
multi-agent
🇷🇺 Russian version: multi-agent.ru.md.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…