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/commands/opensesh/karimo/research)<a href="https://agentmods.dev/commands/opensesh/karimo/research"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/research/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/commands/opensesh/karimo/research"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/research.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.04120 |
| Opus 5.5 | $0.00000 | $0.01648 |
| Sonnet 5.5 | $0.00000 | $0.00824 |
| Haiku 4.5 | $0.00000 | $0.00412 |
Grade C, and why
research scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
3. Start fresh: rm -rf .karimo/prds/{slug} && /karimo:research "{slug}" Copies of this mod
1 near-identical copy found in the catalogue:
- research — 100% identical, 38 lines differ
How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:research
KARIMO Research Command
Purpose
Conduct research to discover codebase patterns, identify gaps, recommend libraries, and provide implementation guidance. This is the REQUIRED first step before planning.
Three research modes:
- Feature Init —
/karimo:research "feature-name"creates PRD folder and runs initial research - PRD-Scoped —
/karimo:research --prd {slug}adds research to existing PRD (iterate loop) - Refinement —
/karimo:research --refine --prd {slug}processes annotations
Command Syntax
# Start new feature (REQUIRED first step)
# Creates PRD folder and runs research
/karimo:research "feature-name"
# Add research to existing PRD (iterate loop after planning)
/karimo:research --prd {slug}
# Refine research based on annotations
/karimo:research --refine --prd {slug}
# Research with constraints
/karimo:research "feature-name" --internal-only
/karimo:research "feature-name" --external-only
/karimo:research --prd {slug} --internal-only
/karimo:research --prd {slug} --external-only
Feature Init Mode (Default)
When invoked with a bare feature name (no --prd flag), this is the first step in the KARIMO workflow.
Workflow
-
Sanitize Feature Name
- Convert
"My Feature Name"tomy-feature-name(slug) - Validate slug format (lowercase, hyphens, no special chars)
- Convert
-
Create PRD Folder Structure
- Create
.karimo/prds/{slug}/(no NNN prefix yet — plan adds it) - Create research subfolder structure:
.karimo/prds/{slug}/ ├── assets/ # Flat folder for screenshots/mockups ├── research/ │ ├── internal/ │ │ ├── patterns.md # Evidence │ │ ├── errors.md # Evidence │ │ ├── dependencies.md # Evidence │ │ ├── structure.md # Evidence │ │ └── findings.md # Consolidated output │ ├── external/ │ │ ├── best-practices.md # Evidence │ │ ├── libraries.md # Evidence │ │ ├── references.md # Evidence │ │ ├── sources.yaml # Attribution │ │ └── findings.md # Consolidated output │ ├── summary.md # Combined executive summary │ └── meta.json # Research metadata └── status.json # Initial status
- Create
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.
- 1mo ago First seen · 500 lines · 0 tokens per session scan C 9c5774e0c4a6
research is a command published in the GitHub repository opensesh/KARIMO (292 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,120 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
code-review
Code review a pull request with BOS design system awareness.
review-pr
Comprehensive PR review using specialized agents.
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
pi-fact-check
Fact-check content via Gemini search + Claude verification — cross-provider claim validation.
pi-askall
Ask both Codex and Gemini the same question — get three perspectives with Claude synthesis.
create
Scaffold a new plugin with directory structure, manifests, and marketplace registration.