karimo-brief-reviewer

karimo-brief-reviewer is an agent for Claude Code from opensesh/KARIMO. It costs 34 tokens per session (2,979 once invoked), scanned A, original, Apache-2.0.

A pre-work review agent that checks a product brief and task instructions against the actual codebase. It records incorrect assumptions, conflicting success requirements, missing settings, and mistaken file-structure expectations.

In plain words
What is it for?
It is for reviewing PRDs, task briefs, project configuration, and optional project learnings, then producing a findings document with evidence and correction guidance.
Why use it?
It helps catch problems in the plan before implementation begins, when they are easier to correct.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the karimo plugin — 11 commands, 22 agents shipped together

Good fit It is for reviewing PRDs, task briefs, project configuration, and optional project learnings, then producing a findings document with evidence and correction guidance.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/opensesh/karimo/brief-reviewer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO

Made for: Claude Code.

Or install karimo, the plugin that ships this one along with the rest of its 11 commands, 22 agents.

Wrote 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.

agentmods badge for karimo-brief-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/opensesh/karimo/brief-reviewer/github.svg)](https://agentmods.dev/agents/opensesh/karimo/brief-reviewer)
Your own site
<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.

agentmods 80×15 button for karimo-brief-reviewer

Your own site · 80×15
<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>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,979 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash d9e661dae42c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

.claude/plugins/karimo/agents/brief-reviewer.md · 400 lines

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:

  1. File state assumptions (e.g., "ESLint rule is 'warn'", "vitest projects configured")
  2. Success criteria (e.g., "lint passes", "test:node passes")
  3. Configuration prerequisites (e.g., "vitest.config.ts has projects array")
  4. File paths and structure (e.g., "src/components/Auth/", "tests/unit/")
  5. Command references (e.g., "npm run lint", "vitest run")
  6. Dependency assumptions (e.g., "Wave 1 must complete before Wave 2")

Step 3: Verify Against Codebase

For each claim:

  1. Use Grep to find actual state (e.g., search ESLint config for rule value)
  2. Use Read to verify file contents (e.g., read vitest.config.ts for projects array)
  3. Use Glob to check paths exist (e.g., verify src/components/Auth/ exists)
  4. Use Bash (read-only) to check commands (e.g., grep '"lint"' package.json)

Read the full file on GitHub · 400 lines

Changes

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.

  1. 9d ago First seen · 400 lines · 34 tokens per session scan A d9e661dae42c

Subscribe to this mod's changes

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.

Related

Other agents, from other repositories