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 commands/opensesh/karimo-overview/researchgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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-overview/research)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/research"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/research.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 | $0.00000 | $0.04127 |
| Opus 5 | $0.00000 | $0.02063 |
| Sonnet 5 | $0.00000 | $0.00825 |
| Haiku 4.5 | $0.00000 | $0.00413 |
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 5d 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}" This is a copy
100% identical to research — 38 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 — 512 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.
- 5d ago First seen · 512 lines · 0 tokens per session scan C 82e198555363
research is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,127 tokens. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to research, differing in 38 lines, and is treated as a copy.
Other commands, from other repositories
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
feedback
Intelligent feedback capture with automatic complexity detection and adaptive investigation.