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/restart.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/restart)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/restart"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/restart.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.00006 | $0.00257 |
| Opus 5 | $0.00003 | $0.00129 |
| Sonnet 5 | $0.00001 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade C, and why
restart scanned grade C 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .next node_modules/.cache What it actually says
Clear all caches and restart the development server for a fresh start.
Steps
-
Kill any running Next.js processes:
pkill -f 'next-server' 2>/dev/null pkill -f 'next dev' 2>/dev/null -
Check cache sizes before clearing (for reporting):
du -sh .next 2>/dev/null du -sh node_modules/.cache 2>/dev/null -
Remove cache directories:
rm -rf .next node_modules/.cache -
Report what was cleared - inform the user how much space was freed.
-
Start the dev server:
npm run dev -
Confirm startup - let the user know the server is running and on which port.
Notes
- This command should be run from the karimo-overview directory
- The
.next/cache can grow to 600+ MB over time - Clearing caches resolves most "stale build" issues
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.
- 6d ago First seen · 41 lines · 6 tokens per session scan C 6126366c121e
restart is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 257 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
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.