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/dashboardgit 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/dashboard)<a href="https://agentmods.dev/commands/opensesh/karimo/dashboard"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/dashboard.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 | $0.00000 | $0.09678 |
| Opus 5 | $0.00000 | $0.04839 |
| Sonnet 5 | $0.00000 | $0.01936 |
| Haiku 4.5 | $0.00000 | $0.00968 |
Grade A, and why
dashboard 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dashboard — 94% identical, 96 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/karimo:dashboard — Comprehensive CLI Dashboard for KARIMO Monitoring
Phase 3 monitoring — System health, execution insights, and velocity analytics.
Usage
/karimo:dashboard # Full dashboard (all 5 sections)
/karimo:dashboard --active # Show only active PRDs with progress
/karimo:dashboard --blocked # Show only blocked tasks
/karimo:dashboard --deps # Show cross-PRD dependency graph
/karimo:dashboard --prd {slug} # PRD-specific dashboard (combines status + metrics)
/karimo:dashboard --alerts # Show only Critical Alerts section (minimal mode)
/karimo:dashboard --activity # Extended activity feed (last 50 events instead of 10)
/karimo:dashboard --gates # Show gate history with condition details (v9.7)
/karimo:dashboard --reconcile # Force git state reconstruction
/karimo:dashboard --json # JSON output for scripting/automation
/karimo:dashboard --refresh # Force refresh (bypass cache)
Purpose
Primary monitoring touchpoint for active development and post-execution analysis.
Provides:
- Executive Summary — System health score, quick stats, next completions
- Critical Alerts — Blocked, stale, crashed tasks needing immediate attention
- Execution Velocity — Completion rate, loop efficiency, wave progress, ETAs
- Resource Usage — Model distribution, loop distribution, parallel capacity
- Recent Activity — Timeline of events across all PRDs
Dashboard Output (Default View)
╭────────────────────────────────────────────────────────────────────╮
│ KARIMO Dashboard Updated: 45s ago │
│ System Health: ████████░░ 85% Active: 2 PRDs │
╰────────────────────────────────────────────────────────────────────╯
📊 QUICK SUMMARY
────────────────
PRDs: 3 total (2 active, 1 complete)
Tasks: 42 total (28 done, 8 running, 4 queued, 2 blocked)
Progress: ████████░░ 67% complete
Models: 28 Sonnet, 12 Opus (30% escalation rate)
✅ Next completions:
• user-profiles Wave 2 (~2h, 1 task remaining)
• token-studio Wave 1 (~6h, 6 tasks queued)
🚨 CRITICAL ALERTS — Needs Immediate Attention
───────────────────────────────────────────────
[user-profiles / 2a] BLOCKED — 3 failed Greptile attempts
→ PR #44 needs human review
→ Blocked for: 2h 15m
→ Action: gh pr view 44
[token-studio / 1c] STALE — Running for 6h 23m
→ Agent may have crashed
→ Action: /karimo:run --prd token-studio --task 1c
Total: 2 items requiring human intervention
📊 EXECUTION VELOCITY — Last 7 Days
────────────────────────────────────
Completion Rate: ████████████░░ 42 tasks (6/day avg)
Loop Efficiency: ████████░░░░░ 2.8 avg (improving ↓)
First-Time Pass: █████░░░░░░░ 45% (↑ from 38%)
Review Pass Rate: ██████████░░ 82% (Greptile avg: 3.2)
Wave Progress:
user-profiles: Wave 2 of 3 ████████░░ 80%
token-studio: Wave 1 of 4 ███░░░░░░░ 25%
ETA Projections:
user-profiles: ~2h (Wave 2: 1 task remaining)
token-studio: ~6h (Wave 1: 6 tasks queued)
⚙️ RESOURCE USAGE — Current Cycle
──────────────────────────────────
Model Distribution: Sonnet: 28 tasks (70%) Opus: 12 tasks (30%)
Escalations: 4 tasks (10% escalation rate)
Parallel Capacity: 2/3 slots utilized (67%)
Loop Distribution:
1 loop: ████████████████ 20 tasks (50%)
2 loops: ████████ 12 tasks (30%)
3 loops: ████ 6 tasks (15%)
4+ loops: ██ 2 tasks (5%) ← Learning candidates
📋 RECENT ACTIVITY — Last 10 Events
────────────────────────────────────
3m ago [user-profiles] Task 2c completed (PR #46 merged)
12m ago [token-studio] Task 1b needs revision (Greptile: 2/5)
15m ago [user-profiles] Wave 2 completed
28m ago [token-studio] Task 1a escalated (sonnet → opus)
1h ago [user-profiles] Task 2b completed (PR #45 merged)
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.
- 4d ago First seen · 1,233 lines · 0 tokens per session scan A 9489676cee4d
dashboard is a command published in the GitHub repository opensesh/KARIMO (283 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 9,678 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
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.
create-plugin
Guided end-to-end plugin creation workflow with component design, implementation, and validation.
test-mcp
Test MCP server connection and all tools.
audit-components
Scan all feature components against the 7 architecture principles in .claude/reference/react-architecture.md, produce a structured report with pass/fail per check, and output a prioritized fix plan.
audit-devprops
Scan the codebase for devProps compliance and produce a structured report grouped by section, with a percentage summary and an explicit exemption list.
feature-dev
Guided feature development with design-first thinking and systematic architecture.