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/feature-devgit clone --depth 1 https://github.com/opensesh/karimo-overviewWhat 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.00011 | $0.01682 |
| Opus 5 | $0.00005 | $0.00841 |
| Sonnet 5 | $0.00002 | $0.00336 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
feature-dev 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development
A systematic 7-phase workflow that helps you build features thoughtfully — from understanding to implementation to review.
You're helping build a new feature or component. Follow this approach: understand first, ask questions, design elegantly, then implement.
For Designers
This workflow mirrors the design process you already know:
- Discovery → Understand the brief
- Research → Explore existing patterns
- Define → Clarify requirements
- Design → Choose an approach
- Build → Implement with care
- Review → Check quality
- Document → Summarize the work
Core Principles
- Ask clarifying questions — Don't assume. Ask specific, concrete questions and wait for answers before implementing.
- Understand before acting — Read and comprehend existing patterns first. For BOS projects, understand our design tokens and component patterns.
- Simple and elegant — Prioritize readable, maintainable code that follows our warm neutrals philosophy.
- Use TodoWrite — Track progress throughout so you can see where you are.
Phase 1: Discovery
Goal: Understand what we're building
Initial request: $ARGUMENTS
Actions:
- Create a todo list with all phases
- If the feature is unclear, ask:
- What problem are we solving? Who is this for?
- What should this feature do? What's the happy path?
- Any constraints? Performance, accessibility, existing patterns to match?
- Summarize your understanding and confirm it's correct
Designer tip: Think of this like the creative brief. Get clear on the "why" before the "what."
Phase 2: Codebase Exploration (Research)
Goal: Understand how similar things work in the codebase
Actions:
-
Launch 2-3 explorer agents to investigate:
- Similar features or components
- Overall architecture and patterns
- UI patterns and styling approaches
Example prompts:
- "Find components similar to [feature] and trace how they're built"
- "Map the design system patterns used in [area]"
- "Analyze how [existing component] handles state and styling"
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.
- 3d ago First seen · 249 lines · 11 tokens per session scan A b1fb91fb99f9
feature-dev is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,682 once invoked, about $0.0001 per session on Opus 5. 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
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
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.
feedback
Intelligent feedback capture with automatic complexity detection and adaptive investigation.