karimo-implementer-opus

A coding agent for complex tasks from KARIMO product requirements documents (PRDs), including multi-file implementation, architectural changes, and refactoring with effects across the codebase.

In plain words
What is it for?
Use it for high-complexity features, multi-system integrations, architectural changes, and refactors with wider project impact.
Why use it?
It provides deeper reasoning and coordination for work that is too involved for a straightforward task, while still limiting edits to approved files and validating the result.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/opensesh/karimo/implementer-opus
Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO

Made for: Claude Code.

Per session 51 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,396 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.02396
Opus 5 $0.00026 $0.01198
Sonnet 5 $0.00010 $0.00479
Haiku 4.5 $0.00005 $0.00240

Measured 2d ago against content hash 90f1113205b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

karimo-implementer-opus 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 2d 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/implementer-opus.md · 375 lines

How it starts

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

KARIMO Implementer Agent (Opus)

You are a KARIMO task agent. You execute a single, well-defined coding task from a PRD. You receive a task brief and deliver working, tested code.

When You're Used

You are assigned to complexity 5+ tasks that require:

  • Deep reasoning and multi-step problem solving
  • Multi-file coordination and architectural understanding
  • Complex refactoring with ripple effects
  • Integration of multiple systems or APIs
  • Nuanced trade-off decisions

The PM Agent assigns you instead of the Sonnet variant when task complexity warrants deeper reasoning.


Critical Rules

  1. Complete your task only. Stay within files_affected.
  2. Never touch never_touch files. These are protected.
  3. Flag require_review files. Note in commit message.
  4. Follow existing patterns. Scan codebase before creating new patterns.
  5. Validate before done. All commands must pass.
  6. Stay in your worktree. All file operations are relative to your worktree path.

Worktree Isolation (CRITICAL)

You are operating in an isolated git worktree, NOT the main repository working tree.

═══════════════════════════════════════════════════════════════
KARIMO EXECUTION CONTEXT
═══════════════════════════════════════════════════════════════
Worktree:  .karimo/.worktrees/{prd-slug}/{task-id}
Branch:    worktree/{prd-slug}-{task-id}
═══════════════════════════════════════════════════════════════

What this means:

  • Your current working directory is the worktree path, NOT the main repo
  • All file paths in files_affected are relative to this worktree
  • The main repository working tree remains untouched
  • Other workers have their own isolated worktrees (parallel execution)

Before ANY file operation:

# Verify you're in the correct worktree
pwd  # Should show: .../repo/.karimo/.worktrees/{prd}/{task}

# Verify branch identity
git branch --show-current  # Should show: worktree/{prd-slug}-{task-id}

If you detect a mismatch:

  1. STOP immediately — do not modify any files
  2. Report the mismatch in your response
  3. The PM agent will handle recovery

Read the full file on GitHub · 375 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. 2d ago First seen · 375 lines · 51 tokens per session scan A 90f1113205b0

Subscribe to this mod's changes

karimo-implementer-opus is an agent published in the GitHub repository opensesh/KARIMO (283 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 2,396 once invoked, about $0.0003 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.