Borrowing it
Nothing to install: this file belongs to opensesh/karimo-overview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensesh/karimo-overview/main/.claude/commands/karimo/configure.mdgit 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/configure)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/configure"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/configure.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.1 | $0.00000 | $0.13837 |
| Opus 5 | $0.00000 | $0.06918 |
| Sonnet 5 | $0.00000 | $0.02767 |
| Haiku 4.5 | $0.00000 | $0.01384 |
Grade B, and why
configure scanned grade B 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 7d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
**Display instructions:** This is a copy
95% identical to configure — 204 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 — 2,023 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:configure — Configuration Command
Create or update KARIMO configuration in .karimo/config.yaml. Use this when you want to configure KARIMO separately from planning.
Usage
/karimo:configure # Basic Mode (default): 3 questions, ~5 min
/karimo:configure --advanced # Advanced Mode: Full control, 9+ questions, ~15 min
/karimo:configure --auto # Auto Mode: Zero prompts, accepts all defaults, <1 min
/karimo:configure --reset # Start fresh, ignore existing config
/karimo:configure --preview # Preview auto-detected config without saving
/karimo:configure --validate # Validate existing config against current project
/karimo:configure --greptile # Install Greptile workflow only
/karimo:configure --code-review # Setup Claude Code Review (instructions only)
/karimo:configure --review # Choose between review providers (interactive)
/karimo:configure --cd # Configure CD provider to skip KARIMO branches
/karimo:configure --check # Show current configuration status
Configuration Modes:
| Mode | Time | Questions | Best For |
|---|---|---|---|
| Basic (default) | ~5 min | 3 | Quick setup, standard projects |
Advanced (--advanced) |
~15 min | 9+ | Custom setup, non-standard projects |
Auto (--auto) |
<1 min | 0 | CI/CD, testing, scripted installs |
This command writes configuration to .karimo/config.yaml (single source of truth).
Source of Truth
.karimo/config.yaml is the authoritative source for KARIMO configuration:
- Agents read config.yaml for runtime, framework, commands, and boundaries
- Learnings are stored separately in
.karimo/learnings/(categorized directories) - CLAUDE.md contains only a minimal reference block (~8 lines)
Behavior
Quick Install: --greptile Flag
When the --greptile flag is passed, skip the full configuration flow and configure Greptile GitHub App integration:
Step 1: Display dashboard setup requirements
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.
- 7d ago First seen · 2,023 lines · 0 tokens per session scan B d4131c49270c
configure 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 13,837 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). It is 95% identical to configure, differing in 204 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.