Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/opensesh/KARIMOnpx agentmods add commands/opensesh/karimo/doctorWrote 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/doctor)<a href="https://agentmods.dev/commands/opensesh/karimo/doctor"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/doctor/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/doctor"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/doctor.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.11139 |
| Opus 5.5 | $0.00000 | $0.04456 |
| Sonnet 5.5 | $0.00000 | $0.02228 |
| Haiku 4.5 | $0.00000 | $0.01114 |
Grade A, and why
doctor scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
LATEST=$(curl -sL "https://api.github.com/repos/opensesh/KARIMO/releases/latest" | grep '"tag_name"' | head -1 | sed 's/.*"v\([^"]*\)".*/\1/') Copies of this mod
1 near-identical copy found in the catalogue:
- doctor — 88% identical, 305 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:doctor — Diagnostic Command
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
Usage
/karimo:doctor # Full diagnostic with recommendations
/karimo:doctor --test # Quick pass/fail verification (replaces /karimo-test)
/karimo:doctor --fix # Clean orphaned worktrees and branches
The --fix flag is the only mode that modifies files.
--test Mode (Quick Verification)
When the --test flag is passed, run a lightweight pass/fail verification instead of the full diagnostic.
Purpose: Verify KARIMO installation works end-to-end without creating real PRDs or spawning agents. This is a lightweight alternative to running a full PRD cycle for verification.
Test Suite
Run these 4 tests:
| Test | Description |
|---|---|
| 1. File Presence | Verify all required files exist per MANIFEST.json |
| 2. Template Parsing | Ensure templates have valid markdown structure |
| 3. GitHub CLI Auth | Verify gh auth status succeeds |
| 4. CLAUDE.md Integration | Verify KARIMO section and config files exist |
Output Format
╭──────────────────────────────────────────────────────────────╮
│ KARIMO Smoke Test │
╰──────────────────────────────────────────────────────────────╯
Test 1: File Presence
─────────────────────
✅ Manifest Present (.karimo/MANIFEST.json)
✅ Agents 22/22 present (from manifest)
✅ Commands 11/11 present (from manifest)
✅ Skills 7/7 present (from manifest)
✅ Templates 18/18 present (from manifest)
Test 2: Template Parsing
────────────────────────
✅ All templates have valid markdown structure
Test 3: GitHub CLI Auth
───────────────────────
✅ Authenticated as @username
Test 4: CLAUDE.md Integration
─────────────────────────────
✅ KARIMO section Present in CLAUDE.md (with markers)
✅ learnings/ Present in .karimo/ (categorized directories)
✅ KARIMO_RULES.md Present in .claude/plugins/karimo/
✅ prds/ directory Exists
Summary
───────
✅ 4/4 tests passed
KARIMO installation verified.
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,450 lines · 0 tokens per session scan A 0a1a015a740e
doctor is a command published in the GitHub repository opensesh/KARIMO (292 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 11,139 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Asks before pushing and creating a PR; --no-pr commits locally without asking.
code-review
Code review a pull request with BOS design system awareness.
review-pr
Comprehensive PR review using specialized agents.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
pi-ask-gemini
Ask Gemini a question — get Google's perspective alongside Claude's.