karimo-tester-opus

karimo-tester-opus is an agent for Claude Code from opensesh/KARIMO. It costs 41 tokens per session (2,431 once invoked), scanned A, original, Apache-2.0.

A testing agent for complex KARIMO tasks, where KARIMO appears to be the surrounding task system. It creates and maintains broad test suites for work that spans several files or systems.

In plain words
What is it for?
Use it for complex testing work, including discovering the current test setup, adding coordinated tests, configuring mocks, and running the full suite before delivery.
Why use it?
It helps cover normal behavior, failures, edge cases, integrations, performance, and security without ignoring the repository's existing testing patterns.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { functionUnderTest } from '../functionUnderTest';.

Part of the karimo plugin — 11 commands, 22 agents shipped together

Good fit Use it for complex testing work, including discovering the current test setup, adding coordinated tests, configuring mocks, and running the full suite before delivery.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO
agentmods
npx agentmods add agents/opensesh/karimo/tester-opus

Made for: Claude Code.

Or install karimo, the plugin that ships this one along with the rest of its 11 commands, 22 agents.

Wrote 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.

agentmods badge for karimo-tester-opus

README.md
[![agentmods](https://agentmods.dev/badge/agents/opensesh/karimo/tester-opus/github.svg)](https://agentmods.dev/agents/opensesh/karimo/tester-opus)
Your own site
<a href="https://agentmods.dev/agents/opensesh/karimo/tester-opus"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/tester-opus/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.

agentmods 80×15 button for karimo-tester-opus

Your own site · 80×15
<a href="https://agentmods.dev/agents/opensesh/karimo/tester-opus"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/tester-opus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 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,431 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00041 $0.02431
Opus 5.5 $0.00016 $0.00972
Sonnet 5.5 $0.00008 $0.00486
Haiku 4.5 $0.00004 $0.00243

Measured 1mo ago against content hash 1d29de9ac059, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/plugins/karimo/agents/tester-opus.md · 425 lines

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

  1. Detect before create. Find existing test framework and patterns FIRST.
  2. Match exactly. Use the same structure, naming, and utilities as existing tests.
  3. Cover the edges. Happy path, error states, null/undefined/empty, boundaries.
  4. Don't break existing tests. Run the full suite before committing.
  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 · 425 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. 1mo ago First seen · 425 lines · 41 tokens per session scan A 1d29de9ac059

Subscribe to this mod's changes

karimo-tester-opus is an agent published in the GitHub repository opensesh/KARIMO (292 stars, last pushed 7d 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.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.