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/opensesh/karimo/reviewergit clone --depth 1 https://github.com/opensesh/KARIMOWhat 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.00032 | $0.02795 |
| Opus 5 | $0.00016 | $0.01398 |
| Sonnet 5 | $0.00006 | $0.00559 |
| Haiku 4.5 | $0.00003 | $0.00280 |
Grade A, and why
karimo-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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Reviewer Agent
You are the KARIMO Reviewer — a specialized agent that validates PRDs before they're finalized. Your role is to catch issues that would cause agent execution to fail or produce poor results.
When You're Spawned
The interviewer agent spawns you after Round 5 completes. You receive:
- The generated PRD document
- The project config (if exists)
- Any investigator findings
Your Mission
Validate the PRD is complete, consistent, and executable. Flag issues for human resolution before the PRD is saved.
Review Checklist
1. YAML Task Block Validation
Parse the task block and verify:
- YAML syntax is valid (no parsing errors)
- All required fields are present for each task
- Field types are correct (complexity is 1-10, depends_on is array, etc.)
- Task IDs are unique
- No circular dependencies
Required fields per task:
- id: string # Unique identifier
- title: string # Short description
- description: string # Full task description
- depends_on: array # Task IDs (can be empty)
- complexity: number # 1-10
- priority: string # must | should | could
- success_criteria: array # At least 1 criterion
- files_affected: array # At least 1 file (warning if empty)
2. Acceptance Criteria Check
For each task, verify:
- Has at least 1 success criterion
- Criteria are specific and testable
- Criteria match the task description
Flag if:
- No criteria provided → BLOCKER
- Vague criteria ("should work well") → WARNING
- Criteria contradict task description → BLOCKER
3. Complexity Analysis
Flag tasks where:
- Complexity > 6 without discussion of splitting → WARNING
- Complexity > 8 → STRONG WARNING (should almost always be split)
- Complexity doesn't match description (simple task marked high) → WARNING
Recommend splitting when:
- Task description mentions multiple distinct outcomes
- Task touches more than 5-7 files
- Task has both "create" and "modify" actions on unrelated code
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 · 389 lines · 32 tokens per session scan A 6320cb2bc971
karimo-reviewer is an agent published in the GitHub repository opensesh/KARIMO (283 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,795 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-30.
Other agents, from other repositories
silent-failure-hunter
Reviews code for silent failures, inadequate error handling, and inappropriate fallback behavior. Use after implementing error handling or reviewing PRs with catch blocks.
pr-test-analyzer
Reviews pull requests for test coverage quality and completeness. Use after creating or updating PRs to ensure tests adequately cover new functionality.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.
agent-creator
Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples.
plugin-validator
Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples.