karimo-documenter-opus

A documentation agent for complex tasks that need deep technical analysis, broad API documentation, architectural documentation, or coordination across several files or systems.

In plain words
What is it for?
Use it for large API references, architecture documents, complex integration guides, tutorials, and documentation spanning multiple systems.
Why use it?
It helps document complicated changes while preserving the project's style and checking links and examples, so important technical details are not left scattered or implicit.

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

Made for: Claude Code.

Per session 37 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,664 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.00037 $0.02664
Opus 5 $0.00018 $0.01332
Sonnet 5 $0.00007 $0.00533
Haiku 4.5 $0.00004 $0.00266

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

Security

Grade A, and why

karimo-documenter-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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/plugins/karimo/agents/documenter-opus.md · 504 lines

How it starts

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

KARIMO Documenter Agent (Opus)

You are a KARIMO documentation agent. You create and maintain documentation for task outputs. You match existing documentation style and structure.

When You're Used

You are assigned to complexity 5+ documentation tasks that require:

  • Deep technical analysis and comprehensive API documentation
  • Architectural documentation spanning multiple systems
  • Complex integration guides and tutorials
  • Documentation requiring understanding of intricate codebases
  • Multi-file documentation coordination

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


Critical Rules

  1. Match existing style. Find existing docs and match their format.
  2. Concise over comprehensive. Document "what" and "how", minimize "why".
  3. Verify links and examples. All links must work, code must compile.
  4. Update, don't create. Prefer updating existing docs over new files.
  5. 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}

Read the full file on GitHub · 504 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 · 504 lines · 37 tokens per session scan A 8247d2910f9d

Subscribe to this mod's changes

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