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/run)<a href="https://agentmods.dev/commands/opensesh/karimo/run"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/run/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/run"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/run.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.08186 |
| Opus 5.5 | $0.00000 | $0.03274 |
| Sonnet 5.5 | $0.00000 | $0.01637 |
| Haiku 4.5 | $0.00000 | $0.00819 |
Grade A, and why
run 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 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.
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 — 1,139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:run — Execute PRD (Recommended)
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
Usage
/karimo:run --prd {slug} [--dry-run] [--skip-review] [--review-only] [--brief-only] [--resume] [--task {id}] [--recalibrate]
Arguments
--prd {slug}(required): The PRD slug to execute--dry-run(optional): Preview the execution plan without making changes--skip-review(optional): Skip brief review and execute immediately--skip-config(optional): Use default execution config without prompting--no-gates(optional): Override gate requirement for large PRDs (v8.3)--review-only(optional): Generate briefs and review, stop without executing--brief-only(optional): Generate briefs only, stop before review--resume(optional): Resume execution after pausing--task {id}(optional): Execute only a specific task by ID--recalibrate(optional): Re-run orchestration inference mid-execution (v9.5)
What This Command Does (5 Phases)
KARIMO v8.2 introduces a 5-phase execution model with user iteration and execution configuration:
┌─────────────────────────────────────────────────────────────┐
│ Phase 1: Brief Generation │
│ Read research + PRD → Generate task briefs │
└─────────────────────────────────────────────────────────────┘
│
↓
┌─────────────────────────────────────────────────────────────┐
│ Phase 2: Auto-Review │
│ Validate briefs → Challenge order/deps → Find gaps │
└─────────────────────────────────────────────────────────────┘
│
↓
┌─────────────────────────────────────────────────────────────┐
│ Phase 3: User Iterate │
│ Present recommendations → User feedback → Adjust briefs │
│ ↺ (loop until approved) │
└─────────────────────────────────────────────────────────────┘
│
↓
┌─────────────────────────────────────────────────────────────┐
│ Phase 3.5: Execution Configuration │
│ Review loops → Bypass rules → Review mode → Confirm │
└─────────────────────────────────────────────────────────────┘
│
↓
┌─────────────────────────────────────────────────────────────┐
│ Phase 4: Orchestrate │
│ Execute tasks in waves → Create PRs → Validate │
└─────────────────────────────────────────────────────────────┘
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 · 1,139 lines · 0 tokens per session scan A b266439630a9
run is a command published in the GitHub repository opensesh/KARIMO (291 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 8,186 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 commands, from other repositories
implement-evidence-asks
Read by /implement Phase 1 (D-CMD-REF-HAND). "The grammar below", "the exception grammar above" and "the record above" name sections of this file. Any other "above" means the Phase 1 text before the step that sent you here.
auto-task
Create an agent team for autonomous workflow: plan (Architect teammate + PM teammate) → develop (Developer teammate + Code-tester teammate + QA-tester teammate + Reviewer teammate) → report (no approval gate).
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-askall
Ask both Codex and Gemini the same question — get three perspectives with Claude synthesis.