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/testergit 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.00040 | $0.02351 |
| Opus 5 | $0.00020 | $0.01175 |
| Sonnet 5 | $0.00008 | $0.00470 |
| Haiku 4.5 | $0.00004 | $0.00235 |
Grade A, and why
karimo-tester 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 3d 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.
This is a copy
89% identical to karimo-tester-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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Tester Agent
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.
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}
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-tests) |
| Title | What you're testing |
| Description | Context on what was implemented |
| Success Criteria | Coverage requirements, specific cases to test |
| Files Affected | Test files you may create/modify |
| Agent Context | Implementation details, edge cases to cover |
| Upstream Findings | Discoveries from the 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.
- 3d ago First seen · 414 lines · 40 tokens per session scan A 87aabc39c3fa
karimo-tester is an agent published in the GitHub repository opensesh/KARIMO (283 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,351 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to karimo-tester-opus, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
test-author
Writes or extends Rust tests for a change in the teamctl workspace, in the same PR as the code. Use when an engineer needs real coverage — happy path, edges, failure modes. Returns the tests plus a coverage note. Follows the repo's existing test patterns.
test_gap_agent
找出 PR/diff 缺失的单测、集成测试、迁移测试和边界用例。.
test-runner
Runs Angular unit tests and reports results with structured output. Use after successful build to verify test suite integrity. Triggers: "run tests", "unit tests", "ng test", "test runner", "check tests", "test suite".
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.