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/plangit 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/plan)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/plan"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/plan.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.05981 |
| Opus 5 | $0.00000 | $0.02991 |
| Sonnet 5 | $0.00000 | $0.01196 |
| Haiku 4.5 | $0.00000 | $0.00598 |
Grade C, and why
plan 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 4d 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. Delete existing: rm -rf .karimo/prds/*_user-auth (caution!) This is a copy
97% identical to plan — 6 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 — 874 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:plan — PRD Interview Command
Start a structured interview to create a Product Requirements Document (PRD) that can be executed by KARIMO agents.
Arguments
(no arguments): Interactive mode — guided flow to start new or resume existing PRD--prd {slug}: Use existing research folder from/karimo:research--skip-research: Allow planning without prior research (not recommended)--resume {slug}: Resume a draft PRD
Voice & Delivery
Do: Present outputs directly without announcing them. Don't: Narrate your actions ("Let me...", "I'm going to...", "I'll show you...")
| Good | Bad |
|---|---|
| [show the welcome message] | "Let me show you the welcome message, then we'll check configuration." |
| "Codebase scan available. Proceed? [Y/n]" | "Would you like me to scan the codebase?" |
| "Configuration required." | "I need to check if configuration exists first." |
| "Generate PRD now? [Y/n]" | "Ready for me to generate the PRD?" |
Present content, prompts, and options directly. Users see actions happen — they don't need narration.
Behavior
v7.0 Workflow Change
Research is now required before planning.
The workflow is:
/karimo:research "feature-name"— Creates folder, runs research/karimo:plan --prd feature-name— Uses research, creates PRD
To skip research (not recommended):
/karimo:plan --prd feature-name --skip-research
Interactive Mode (No Arguments)
If no --prd flag provided, enter interactive mode:
Step 1: Main Menu
╭──────────────────────────────────────────────────────╮
│ KARIMO Planning │
╰──────────────────────────────────────────────────────╯
What would you like to do?
1. Start a new feature
2. Resume an existing PRD
Your choice:
Step 2a: New Feature Flow (Option 1)
-
Prompt for feature name:
What's the feature you want to build? Feature name: -
Sanitize input to slug (lowercase, hyphens)
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.
- 4d ago First seen · 874 lines · 0 tokens per session scan C 3de7b9507640
plan 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 5,981 tokens. A static security scan graded it C with 1 finding (recursive force delete). It is 97% identical to plan, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
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.