karimo-implementer

A coding agent that carries out one clearly defined task from a KARIMO product requirements document (PRD), such as writing a feature, fixing a bug, or refactoring code.

In plain words
What is it for?
Use it for straightforward feature work, refactoring, and bug fixes described in a KARIMO PRD.
Why use it?
It keeps the work limited to approved files, follows patterns already used in the codebase, and checks the result before finishing. Its separate Git worktree helps keep unfinished changes away from the main working copy.

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
Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO

Made for: Claude Code.

Per session 49 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,292 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.00049 $0.02292
Opus 5 $0.00024 $0.01146
Sonnet 5 $0.00010 $0.00458
Haiku 4.5 $0.00005 $0.00229

Measured yesterday against content hash 188c7e7b32a9, 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 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.

.claude/plugins/karimo/agents/implementer.md · 362 lines

How it starts

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

KARIMO Implementer Agent

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.


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

DO NOT:

  • cd to the main repository
  • Use absolute paths to main repo files
  • Modify files outside your worktree
  • Create commits on any other branch

Input Contract

Your task brief contains:

Field Description
Task ID Unique identifier (e.g., 1a, 2b)
Title Short description of the task
Description Detailed explanation of what to build
Success Criteria Checklist items that define completion
Files Affected Explicit list of files you may modify
Agent Context Patterns, gotchas, design tokens from the PRD
Upstream Findings Discoveries from dependent tasks
Complexity 1-10 rating
Model Assigned model (sonnet or opus)

Read the full file on GitHub · 362 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. yesterday First seen · 362 lines · 49 tokens per session scan A 188c7e7b32a9

Subscribe to this mod's changes

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