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/xsovad06/sova/new-featuregit clone --depth 1 https://github.com/xsovad06/sovaWhat 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.00014 | $0.00409 |
| Opus 5 | $0.00007 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
new-feature 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 2d 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
Start New Feature
Set up a new feature branch and prepare for development.
Feature name/description: $ARGUMENTS
Workflow
1. Ensure Clean Starting Point
- Verify we are on
main:git branch --show-current - Ensure working tree is clean:
git status - Pull latest:
git pull origin main
2. Create Feature Branch
- Derive a branch name from the description (lowercase, hyphenated)
- Features:
feat/<name>(e.g.,feat/income-crud) - Fixes:
fix/<name>(e.g.,fix/currency-conversion) - Refactors:
refactor/<name>(e.g.,refactor/auth-flow)
- Features:
- Create and switch:
git checkout -b <branch-name>
3. Review Context
- Read CLAUDE.md and AGENTS.md for project conventions
- Read agent memory files if they exist (
.claude/agent-memory/) - Identify which existing modules/files will be affected
4. Plan
- Break the feature into concrete implementation tasks
- Create a TodoWrite list with the tasks
- Identify any dependencies or prerequisites
5. Report
Tell the user:
- Branch name created
- High-level implementation plan
- Which files/modules will be affected
- Any questions or ambiguities to resolve before starting
- Suggest running
/develop <description>to begin implementation
Cross-References
- Ready to implement? Run
/develop <description>or/develop-full <description> - Need to understand approaches first? Run
/develop-explain <description>
Rules
- NEVER use emojis in any output
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.
- 2d ago First seen · 58 lines · 14 tokens per session scan A e1771b833f7a
new-feature is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 409 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-31.
Other commands, from other repositories
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.
pr-description-ja
現在のブランチの変更内容を分析し、日本語で包括的なPull Request descriptionを生成してください。.
pr-description-en
Auto-generate PR description in English from changes against base branch.