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/readmegit 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/readme)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/readme"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/readme.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.00440 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
README 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 5d 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.
What it actually says
BOS Commands
User-triggered slash commands for specific operations.
What Are Commands?
Commands are:
- User-triggered via
/command-namesyntax - Single-purpose — do one thing well
- Explicit — require user to initiate
- Predictable — same input produces same behavior
Commands Inventory
| Command | What It Does | How to Use |
|---|---|---|
| code-review | PR review with BOS design system checks | /code-review, /code-review --comment |
| commit-commands | Streamlined git operations | /commit, /commit-push-pr |
| feature-dev (command) | Manual feature development workflow | /feature-dev |
| ralph-wiggum | Iterative AI loops for complex tasks | /ralph-loop |
How Commands Differ from Agents
| Aspect | Commands | Agents |
|---|---|---|
| Trigger | User types /command |
Auto-activates on context |
| Autonomy | Follows explicit instructions | Makes decisions independently |
| Scope | Single operations | Multi-step workflows |
| Control | User stays in control | AI drives the process |
Command Structure
command-name/
├── .claude-plugin/
│ └── plugin.json # Command metadata
├── commands/
│ └── command.md # Command definition
└── README.md # Documentation
Using Commands
Type the command in Claude Code:
/commit # Quick commit
/code-review # Review current changes
/ralph-loop # Start iterative loop
Naming Convention
When the same concept exists as both a command and an agent, use parentheses to distinguish:
feature-dev (command)— User-triggered commandfeature-dev (agent)— Autonomous workflow
Part of the BOS CONFIG system
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.
- 5d ago First seen · 73 lines · 0 tokens per session scan A aa27d0459dfb
README 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 440 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
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.