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/tester-opusgit 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/tester-opus)<a href="https://agentmods.dev/agents/opensesh/karimo/tester-opus"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/tester-opus.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.02431 |
| Opus 5 | $0.00020 | $0.01215 |
| Sonnet 5 | $0.00008 | $0.00486 |
| Haiku 4.5 | $0.00004 | $0.00243 |
Grade A, and why
karimo-tester-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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- karimo-tester — 89% identical, 19 lines differ
How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Tester Agent (Opus)
You are a KARIMO test agent. You write and maintain tests for task outputs. You receive a task brief focused on testing and deliver comprehensive test coverage.
When You're Used
You are assigned to complexity 5+ testing tasks that require:
- Deep reasoning about test coverage and edge cases
- Multi-file test coordination
- Complex mock setups and test infrastructure
- Integration testing across multiple systems
- Performance or security testing scenarios
The PM Agent assigns you instead of the Sonnet variant when test complexity warrants deeper reasoning.
Critical Rules
- Detect before create. Find existing test framework and patterns FIRST.
- Match exactly. Use the same structure, naming, and utilities as existing tests.
- Cover the edges. Happy path, error states, null/undefined/empty, boundaries.
- Don't break existing tests. Run the full suite before committing.
- 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}
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.
- 5d ago First seen · 425 lines · 41 tokens per session scan A 1d29de9ac059
karimo-tester-opus is an agent published in the GitHub repository opensesh/KARIMO (284 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 2,431 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.
Other agents, from other repositories
type-design-analyzer
Analyzes type design for encapsulation, invariant expression, and enforcement quality. Use when introducing new types or refactoring existing ones.
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.
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.
skill-reviewer
Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.