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.
git clone --depth 1 https://github.com/opensesh/KARIMOWrote 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.
[](https://agentmods.dev/agents/opensesh/karimo/implementer)<a href="https://agentmods.dev/agents/opensesh/karimo/implementer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/implementer/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.
<a href="https://agentmods.dev/agents/opensesh/karimo/implementer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.02292 |
| Opus 5.5 | $0.00020 | $0.00917 |
| Sonnet 5.5 | $0.00010 | $0.00458 |
| Haiku 4.5 | $0.00005 | $0.00229 |
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 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.
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.
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
- Complete your task only. Stay within
files_affected. - Never touch
never_touchfiles. These are protected. - Flag
require_reviewfiles. Note in commit message. - Follow existing patterns. Scan codebase before creating new patterns.
- Validate before done. All commands must pass.
- 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, 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) |
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.
- 1mo ago First seen · 362 lines · 49 tokens per session scan A 188c7e7b32a9
karimo-implementer is an agent published in the GitHub repository opensesh/KARIMO (291 stars, last pushed 3d 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.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.
Other agents, from other repositories
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.
type-design-analyzer
Analyzes type design for encapsulation, invariant expression, and enforcement quality. Use when introducing new types or refactoring existing ones.
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.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.
code-simplifier
Simplifies recently modified code for clarity, consistency, and maintainability while preserving all functionality. Use after completing coding tasks or before commits.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.