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/prgit 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.00021 | $0.02321 |
| Opus 5 | $0.00010 | $0.01161 |
| Sonnet 5 | $0.00004 | $0.00464 |
| Haiku 4.5 | $0.00002 | $0.00232 |
Grade A, and why
pr 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create a pull request for the current branch using the project's standard PR template.
# Benchmark logging (entry)
bash .claude/benchmark/log.sh "pr_start" "" "" 2>/dev/null || true
Instructions
-
Update main branch and rebase:
- Stash any uncommitted changes first (if any):
git stash push -m "Pre-rebase stash" - Fetch latest:
git fetch origin - Update local main:
git checkout main && git pull origin main(adjust branch name if project usesmaster) - Check for local-only main commits:
git rev-list --count origin/main..main-- if non-zero, warn the user: "local main is N commits ahead of origin/main -- these will leak into PR scope. Rungit reset --hard origin/mainto fix." - Switch back to feature branch:
git checkout - - Rebase onto updated main:
git rebase main - Handle rebase conflicts (if any): Inform the user and help resolve them
- Pop the stashed changes (if any):
git stash pop
- Stash any uncommitted changes first (if any):
-
Gather branch information by running these commands in parallel:
git status-- check for uncommitted changesgit branch --show-current-- get current branch namegit log origin/main..HEAD --oneline-- list all commits on this branchgit diff origin/main...HEAD --stat-- summary of all committed changesgit diff --stat-- summary of uncommitted changesgh pr list --head $(git branch --show-current) --json number,url,state-- check if PR already exists
-
Handle existing PR: If a PR already exists, ASK THE USER which workflow they want:
- Option A: AI feedback workflow -- reset and recreate all commits (soft reset to main, reorganize)
- Option B: Incremental workflow -- add new commits on top
-
Handle main branch (if current branch is main/master):
- Create a new feature branch from changes
- Generate a descriptive branch name (e.g.,
fix/lint-errors,feat/add-caching) - Continue PR process on the new branch
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 · 212 lines · 21 tokens per session scan A d7867ba9961a
pr is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,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
align
Unified alignment command (--project, --docs, --retrofit, --content).
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.