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/configure)<a href="https://agentmods.dev/commands/opensesh/karimo/configure"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/configure/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/configure"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/configure.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.16125 |
| Opus 5.5 | $0.00000 | $0.06450 |
| Sonnet 5.5 | $0.00000 | $0.03225 |
| Haiku 4.5 | $0.00000 | $0.01613 |
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 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.
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:** Copies of this mod
1 near-identical copy found in the catalogue:
- configure — 95% identical, 204 lines differ
How it starts
The opening of the file, as written. The whole thing — 2,306 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
/karimo:configure --subscription # Configure Claude subscription for usage estimation
Configuration Modes:
| Mode | Time | Questions | Best For |
|---|---|---|---|
| Basic (default) | ~5 min | 4 | Quick setup, standard projects |
Advanced (--advanced) |
~15 min | 10+ | 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:
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 · 2,306 lines · 0 tokens per session scan B 918336e7377f
configure is a command published in the GitHub repository opensesh/KARIMO (292 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 16,125 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). 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.