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/plan)<a href="https://agentmods.dev/commands/opensesh/karimo/plan"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/plan/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/plan"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/plan.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.06028 |
| Opus 5.5 | $0.00000 | $0.02411 |
| Sonnet 5.5 | $0.00000 | $0.01206 |
| Haiku 4.5 | $0.00000 | $0.00603 |
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 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. Delete existing: rm -rf .karimo/prds/*_user-auth (caution!) Copies of this mod
1 near-identical copy found in the catalogue:
- plan — 97% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 876 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.
- 1mo ago First seen · 876 lines · 0 tokens per session scan C 9a31cac8d5a4
plan is a command published in the GitHub repository opensesh/KARIMO (292 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,028 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.