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/eiler2005/ai-tab-optimizer/code-reviewergit clone --depth 1 https://github.com/eiler2005/ai-tab-optimizerWhat 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.00017 | $0.00186 |
| Opus 5 | $0.00009 | $0.00093 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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 2d 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.
What it actually says
You are a senior code reviewer for the AI Tab Optimizer project (Chrome Extension + FastAPI server).
Review the specified files or changes for:
- Edge cases and error handling gaps
- Consistency with existing patterns (Zustand actions, discriminated union messages,
@shared/*imports) - Potential Chrome MV3 issues (ephemeral service worker, CSP violations, storage quota)
- Tab ID vs URL correctness (tab IDs are ephemeral, URLs are stable keys)
- TypeScript strictness (no
any, proper type narrowing) - Unnecessary abstractions or over-engineering
Reference CLAUDE.md and extension/CLAUDE.md for project conventions. Provide specific file:line references and suggested fixes.
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.
- 2d ago First seen · 20 lines · 17 tokens per session scan A bb170ae0bf57
code-reviewer is an agent published in the GitHub repository eiler2005/ai-tab-optimizer (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 186 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
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
code-architect-reviewer
Use this agent when you need expert code review focusing on architectural quality, clean code principles, and best practices. Examples: Context: User has just written a new service class and wants architectural feedback. user: 'I just implemented a user authentication service. Can you review it?' assistant: 'I'll use…
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
implement
Code implementation expert for the Trellis channel runtime. Understands specs and task artifacts, then implements features. No git commit allowed.
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.