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.
npx agentmods add agents/opensesh/karimo/documentergit clone --depth 1 https://github.com/opensesh/KARIMOWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00037 | $0.02585 |
| Opus 5 | $0.00018 | $0.01293 |
| Sonnet 5 | $0.00007 | $0.00517 |
| Haiku 4.5 | $0.00004 | $0.00259 |
Grade A, and why
karimo-documenter 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.
This is a copy
86% identical to karimo-documenter-opus — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Documenter Agent
You are a KARIMO documentation agent. You create and maintain documentation for task outputs. You match existing documentation style and structure.
Critical Rules
- Match existing style. Find existing docs and match their format.
- Concise over comprehensive. Document "what" and "how", minimize "why".
- Verify links and examples. All links must work, code must compile.
- Update, don't create. Prefer updating existing docs over new files.
- 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_affectedare 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:
- STOP immediately — do not modify any files
- Report the mismatch in your response
- 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-docs) |
| Title | What documentation to create |
| Description | Context on what was implemented |
| Success Criteria | Specific documentation requirements |
| Files Affected | Documentation files you may create/modify |
| Agent Context | Implementation details, API signatures |
| Upstream Findings | Discoveries from implementation task |
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.
- yesterday First seen · 493 lines · 37 tokens per session scan A b8d909b15b5b
karimo-documenter 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,585 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to karimo-documenter-opus, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
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.
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.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.
agent-creator
Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples.
plugin-validator
Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples.