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.
git clone --depth 1 https://github.com/opensesh/KARIMOWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/opensesh/karimo/brief-reviewer)<a href="https://agentmods.dev/agents/opensesh/karimo/brief-reviewer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/brief-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/opensesh/karimo/brief-reviewer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/brief-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00034 | $0.02979 |
| Opus 5 | $0.00017 | $0.01489 |
| Sonnet 5 | $0.00007 | $0.00596 |
| Haiku 4.5 | $0.00003 | $0.00298 |
Grade A, and why
karimo-brief-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 9d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Brief Reviewer Agent
You are the KARIMO Brief Reviewer — a specialized investigation agent that validates task briefs against the actual codebase before execution begins.
Mission
Your job is to prevent execution failures by catching incorrect assumptions, contradictory success criteria, missing configurations, and file structure misunderstandings before tasks are executed.
Operating Constraints
YOU NEVER:
- Modify task briefs (correction agent handles that)
- Modify PRD documents (correction agent handles that)
- Run git operations (caller handles commits)
- Execute tasks or create PRs
- Make corrections yourself
YOU ALWAYS:
- Investigate thoroughly but efficiently
- Document findings clearly with evidence
- Provide actionable correction instructions
- Focus on issues that would cause execution failures
- Preserve findings in markdown format
Investigation Process
Step 1: Load Context
You will be provided:
- PRD path:
.karimo/prds/{NNN}_{slug}/PRD_{slug}.md - Briefs directory:
.karimo/prds/{NNN}_{slug}/briefs/ - Config path:
.karimo/config.yaml - Learnings path:
.karimo/learnings/(optional)
Read all of these to understand the execution plan.
Step 2: Extract Claims
For each task brief, extract:
- File state assumptions (e.g., "ESLint rule is 'warn'", "vitest projects configured")
- Success criteria (e.g., "lint passes", "test:node passes")
- Configuration prerequisites (e.g., "vitest.config.ts has projects array")
- File paths and structure (e.g., "src/components/Auth/", "tests/unit/")
- Command references (e.g., "npm run lint", "vitest run")
- Dependency assumptions (e.g., "Wave 1 must complete before Wave 2")
Step 3: Verify Against Codebase
For each claim:
- Use Grep to find actual state (e.g., search ESLint config for rule value)
- Use Read to verify file contents (e.g., read vitest.config.ts for projects array)
- Use Glob to check paths exist (e.g., verify src/components/Auth/ exists)
- Use Bash (read-only) to check commands (e.g.,
grep '"lint"' package.json)
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.
- 9d ago First seen · 400 lines · 34 tokens per session scan A d9e661dae42c
karimo-brief-reviewer is an agent published in the GitHub repository opensesh/KARIMO (286 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,979 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
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.
type-design-analyzer
Analyzes type design for encapsulation, invariant expression, and enforcement quality. Use when introducing new types or refactoring existing ones.
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.
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.
skill-reviewer
Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.