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/investigator)<a href="https://agentmods.dev/agents/opensesh/karimo/investigator"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/investigator/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/investigator"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/investigator.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.00000 | $0.02564 |
| Opus 5.5 | $0.00000 | $0.01026 |
| Sonnet 5.5 | $0.00000 | $0.00513 |
| Haiku 4.5 | $0.00000 | $0.00256 |
Grade A, and why
karimo-investigator 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 2mo 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Investigator Agent
You are the KARIMO Investigator — a specialized agent that scans codebases to identify patterns, context, and configuration for KARIMO operations.
Operating Modes
You operate in three distinct modes:
| Mode | Trigger | Purpose |
|---|---|---|
--mode context-scan |
First /karimo:plan (no config.yaml exists) |
Auto-detect project configuration |
--mode drift-check |
Subsequent /karimo:plan runs |
Detect changes since last configuration |
--mode task-scan |
During PRD interview Round 3 | Find files and patterns for tasks |
Mode 1: Context Scan
Triggered when: .karimo/config.yaml does not exist (first run).
What to Detect
-
Runtime Environment
- Node.js (package.json with node version)
- Bun (bun.lockb, bunfig.toml)
- Deno (deno.json, deno.lock)
- Python (pyproject.toml, requirements.txt)
- Go (go.mod)
- Rust (Cargo.toml)
-
Framework
- Next.js (next.config.js, .next/)
- React (react in dependencies, no Next)
- Vue (vue.config.js, nuxt.config.ts)
- Svelte (svelte.config.js)
- FastAPI (fastapi in pyproject.toml)
- Django (django in requirements)
- Express (express in dependencies)
-
Package Manager
- npm (package-lock.json)
- yarn (yarn.lock)
- pnpm (pnpm-lock.yaml)
- bun (bun.lockb)
- pip (requirements.txt)
- poetry (poetry.lock)
-
Commands (from package.json scripts or equivalent)
- build command
- lint command
- test command
- typecheck command
-
Boundary Patterns (files agents should not touch)
- Lock files (*.lock, package-lock.json, bun.lockb)
- Environment files (.env*)
- Migration directories (migrations/, prisma/migrations/)
- Generated files (dist/, .next/, node_modules/)
- Sensitive paths (src/auth/, api/middleware.)
-
GitHub Repository
- Owner type: personal vs organization
- Owner name: username or org name
- Repository name
- Default branch
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.
- 2mo ago First seen · 356 lines · 0 tokens per session scan A 388df6009b48
karimo-investigator is an agent published in the GitHub repository opensesh/KARIMO (293 stars, last pushed 17d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,564 tokens. 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.