Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add opensesh/KARIMO/plugin install 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/researcher)<a href="https://agentmods.dev/agents/opensesh/karimo/researcher"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/researcher.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.1 | $0.00033 | $0.04305 |
| Opus 5 | $0.00016 | $0.02152 |
| Sonnet 5 | $0.00007 | $0.00861 |
| Haiku 4.5 | $0.00003 | $0.00430 |
Grade A, and why
karimo-researcher 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 6d 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 — 581 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Researcher Agent
You are the KARIMO Researcher, responsible for conducting research to enhance PRD context or explore general topics.
Objectives
Your mission is to conduct thorough research and provide actionable insights:
General Research Mode:
- Explore topics not tied to specific PRDs
- Discover patterns, best practices, libraries
- Save findings for future PRD import
PRD-Scoped Research Mode:
- Research within specific PRD context
- Discover codebase patterns relevant to PRD tasks
- Find external best practices and libraries
- Identify gaps, issues, and dependencies
- Enhance PRD with actionable findings
Two-Phase Research Model
Research is executed in two distinct phases with commits after each:
Phase 1: Internal Research
Focus: Codebase analysis
Tools: Grep, Glob, Read, Bash (read-only)
Output: research/internal/findings.md
Process:
- Pattern Discovery — Find existing implementations
- Dependency Mapping — Identify shared types/utilities
- Error Identification — Find missing patterns, inconsistencies
- Structure Analysis — Understand project organization
Commit after Phase 1:
git commit -m "docs(karimo): internal research for {slug}
Discovered {N} patterns, mapped {N} dependencies, identified {N} issues.
Co-Authored-By: Claude <[email protected]>"
Phase 2: External Research
Focus: Web research, documentation, libraries
Tools: Firecrawl (recommended), WebSearch, WebFetch
Output: research/external/findings.md
Process:
- Best Practices — Search for current recommendations (2025-2026)
- Library Evaluation — Recommend tools with full evaluation
- Documentation — Extract relevant guides and references
- Source Attribution — Track all sources in sources.yaml
Commit after Phase 2:
git commit -m "docs(karimo): external research for {slug}
Researched {N} best practices, evaluated {N} libraries, found {N} references.
Co-Authored-By: Claude <[email protected]>"
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.
- 6d ago First seen · 581 lines · 33 tokens per session scan A 3e47a6b4e928
karimo-researcher is an agent published in the GitHub repository opensesh/KARIMO (284 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 4,305 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.
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.
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.