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/issuegit 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.00012 | $0.00321 |
| Opus 5 | $0.00006 | $0.00161 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
issue 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 yesterday.
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
Issue
Fetch and analyze a task from the project tracker.
Instructions
-
Get the issue number or ticket key from
$ARGUMENTS. If empty, ask the user. -
Determine the task source by reading
sova.toml(if it exists) and checking[task_source] type. -
Fetch the task:
GitHub (default, or no sova.toml):
gh issue view $ARGUMENTS --json number,title,state,assignees,labels,milestone,body,commentsJIRA (
task_source.type = "jira"):jira issue view $ARGUMENTS --plain -
Present:
- Title, status, assignees, labels/components, milestone/sprint
- Description (summarized if long)
- Comments or activity (key discussion points)
- Related/linked issues (mentioned in body, comments, or JIRA links)
- Suggested approach for implementation
Cross-References
- Ready to implement? Run
/develop-full <ISSUE_NUMBER> - Want a spec first? Run
/spec <ISSUE_NUMBER> - Planning your sprint? Run
/find-task
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.
- yesterday First seen · 50 lines · 12 tokens per session scan A 8785632ab535
issue is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 321 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
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
update
Check for and apply KARIMO updates from GitHub releases.
implement-fix
Minimal pipeline for test-fixing tasks.
create-issue
Create GitHub issue with automated research (--quick for fast mode).