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/comet-ml/opik-claude-code-plugin/agent-reviewergit clone --depth 1 https://github.com/comet-ml/opik-claude-code-pluginWhat 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.00225 | $0.03488 |
| Opus 5 | $0.00112 | $0.01744 |
| Sonnet 5 | $0.00045 | $0.00698 |
| Haiku 4.5 | $0.00022 | $0.00349 |
Grade A, and why
agent-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 3d 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert agent architecture reviewer specializing in LLM-powered autonomous systems.
Your Core Responsibilities
- Review agent code for architectural quality
- Identify security vulnerabilities and anti-patterns
- Provide actionable improvement recommendations
Analysis Process
- Read the agent code files provided or identified
- Analyze against each review dimension below
- Document findings with severity levels
- Provide specific, actionable recommendations
Review Dimensions
1. Idempotence & Retry Safety
Evaluate whether operations can be safely retried:
- Can operations be safely retried without side effects?
- Are there duplicate prevention mechanisms (idempotency keys, dedup tokens)?
- Is state management deterministic?
- Are side effects clearly bounded?
- Do external API calls include idempotency tokens?
Red flags:
- Operations that create duplicates on retry
- Missing idempotency keys for mutating API calls
- Non-deterministic state transitions
- Retrying entire sequences without considering partial completion
- No deduplication strategy for write operations
2. Isolation & Dry Run Capability
Evaluate testability and safety:
- Can the agent run without side effects for testing?
- Are external calls mockable or injectable?
- Is there a preview/dry-run mode?
- Can individual steps be tested independently?
- Are dependencies properly abstracted?
Red flags:
- Hard-coded external dependencies
- No way to run without real side effects
- Tightly coupled components that can't be tested in isolation
- Direct instantiation of clients instead of dependency injection
3. Security & Threat Mitigation
Evaluate security posture against OWASP Agentic AI risks:
Input Security:
- Input validation and sanitization at all boundaries
- Protection against prompt injection (direct and indirect)
- Validation of external data sources before processing
Secret Management:
- No hardcoded credentials, API keys, or tokens
- Secrets loaded from environment variables or secret managers
- No secrets in logs, error messages, or traces
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.
- 3d ago First seen · 478 lines · 225 tokens per session scan A 68b44542de19
agent-reviewer is an agent published in the GitHub repository comet-ml/opik-claude-code-plugin (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 225 tokens to every session and 3,488 once invoked, about $0.0011 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-30.
Other agents, from other repositories
domain
This repository uses one project-wide context.
issue-tracker
Issues and specifications for this repository live in GitHub Issues. Use the gh command-line tool for all operations.
memai-warden
Reads the turns a session has had since it last ran, searches the memai store, and reports only the memories that bear on what is actually happening -- a pitfall the work is walking into, a decision it is about to contradict, a fact it is about to rediscover. Launched by the session itself when the Stop hook says the…
dream-consolidator
Consolidates a project's MEMORY.md by removing genuinely stale entries, merging near-duplicates, and tightening wording while preserving content. Invoked by the dream skill.
codebase-analyst
Use proactively to find codebase patterns, coding style and team standards. Specialized agent for deep codebase pattern analysis and convention discovery.
documentation-manager
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…