karimo-pm

karimo-pm is an agent for Claude Code from opensesh/KARIMO. It costs 40 tokens per session (21,250 once invoked), scanned C, original, Apache-2.0.

A project-coordination agent that runs planned coding tasks by assigning work to other agents and managing their pull requests.

In plain words
What is it for?
It helps execute tasks in dependency order, monitor workers, coordinate reviews, handle stalled work, and merge completed changes.
Why use it?
It keeps multi-step implementation work ordered and tracked without directly editing the application code.

Agent for Claude Code

Written for Claude Code: SubagentStop hook event. Also seen: model in frontmatter; reads .claude/ paths; positional $N argument.

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

Good fit It helps execute tasks in dependency order, monitor workers, coordinate reviews, handle stalled work, and merge completed changes.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/opensesh/karimo/pm
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-pm

README.md
[![agentmods](https://agentmods.dev/badge/agents/opensesh/karimo/pm/github.svg)](https://agentmods.dev/agents/opensesh/karimo/pm)
Your own site
<a href="https://agentmods.dev/agents/opensesh/karimo/pm"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/pm/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-pm

Your own site · 80×15
<a href="https://agentmods.dev/agents/opensesh/karimo/pm"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 21,250 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00040 $0.21250
Opus 5.5 $0.00016 $0.08500
Sonnet 5.5 $0.00008 $0.04250
Haiku 4.5 $0.00004 $0.02125

Measured 1mo ago against content hash d35750724ab8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

karimo-pm scanned grade C with 1 finding 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$worktree_path"
.claude/plugins/karimo/agents/pm.md · 2,447 lines

How it starts

The opening of the file, as written. The whole thing — 2,447 lines — stays where its author put it; the contents beside it link to each section on GitHub.

KARIMO PM Agent (Team Coordinator)

You are the KARIMO PM Agent — a specialized coordinator that manages autonomous task execution for a single PRD. You orchestrate worker agents, manage wave-ordered execution, and ensure tasks complete successfully with PRs merged to main.

Critical Rule

You NEVER write code. Your role is coordination only. You:

  • Parse and plan execution from the PRD
  • Spawn worker agents with task briefs
  • Spawn PM-Reviewer for review loops
  • Spawn PM-Finalizer for cleanup
  • Monitor progress via PR state
  • Propagate findings between waves
  • Handle stalls and model escalation
  • Manage PR lifecycle through merge

If you find yourself about to write application code, STOP and spawn a worker agent instead.


Agent Topology (v9.1)

The PM orchestrator delegates to two specialized agents:

Agent Responsibility When Spawned
PM-Reviewer Review loops, model escalation Per task PR (when review configured)
PM-Finalizer Cleanup, metrics, finalization Once after all waves complete

This decomposition keeps the PM agent focused on orchestration while specialized agents handle complex sub-flows.


Your Scope

You operate within one PRD. Everything you manage lives under:

.karimo/prds/{NNN}_{slug}/
├── PRD_{slug}.md       # Narrative document (your reference)
├── tasks.yaml          # Task definitions (your execution plan)
├── execution_plan.yaml # Wave-based execution plan
├── status.json         # Execution state (your single source of truth)
├── findings.md         # Cross-task discoveries (you maintain this)
├── briefs/             # Pre-generated briefs per task
│   ├── 1a_{slug}.md
│   ├── 1b_{slug}.md
│   └── ...
└── assets/             # Images from interview

When You're Spawned

The /karimo:run command spawns you with:

  • Project configuration from .karimo/config.yaml and .karimo/learnings/
  • PRD content (tasks, execution plan, narrative)
  • Current status (for resume scenarios)
  • Execution mode (full PRD or single task via --task {id})

Read the full file on GitHub · 2,447 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. 1mo ago First seen · 2,447 lines · 40 tokens per session scan C d35750724ab8

Subscribe to this mod's changes

karimo-pm is an agent published in the GitHub repository opensesh/KARIMO (291 stars, last pushed 3d ago), licensed Apache-2.0. It adds 40 tokens to every session and 21,250 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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

Tracker

Background tracker-conventions agent — probes the configured issue tracker's capabilities, infers repository conventions within bounds, and writes that provider's /.devflow/tracker/{provider}.md exactly once. Spawned only by the session-start setup directive; never invoked from a command or another agent.

dean0x/devflow · 59 tokens

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.

opensesh/karimo-overview · 30 tokens

nazgul:self-audit

Post-loop, proposes-only self-audit — mines objective cost/perf/correctness signals via ${CLAUDEPLUGINROOT}/scripts/self-audit.sh and appends structured findings to the main worktree's improvements backlog. Never edits code or approves anything; writes only its own completion marker.

OrodruinLabs/nazgul · 65 tokens

type-design-analyzer

Analyzes type design for encapsulation, invariant expression, and enforcement quality. Use when introducing new types or refactoring existing ones.

opensesh/karimo-overview · 31 tokens

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.

opensesh/karimo-overview · 34 tokens

comment-analyzer

Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.

opensesh/karimo-overview · 33 tokens