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/sprint-plangit 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.00016 | $0.00464 |
| Opus 5 | $0.00008 | $0.00232 |
| Sonnet 5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
sprint-plan 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
Sprint Planning
Review your assigned GitHub Issues, prioritize them, and manage your sprint queue.
Instructions
-
Fetch assigned issues:
gh issue list --assignee @me --state open --limit 50 --json number,title,labels,milestone,updatedAt,bodyIf the project uses GitHub Projects, also fetch board state:
gh project item-list --owner <OWNER> --format json 2>/dev/null || true -
Categorize by status:
- Active work: issues with in-progress labels or linked open PRs
- Queued: assigned but not started (backlog, ready)
- Needs refinement: issues with vague descriptions or missing acceptance criteria
- Blocked: issues with blocker labels or dependency on other issues
-
For each issue, provide:
- Issue number, title, current labels
- Estimated effort: small / medium / large (based on title and description)
- Dependencies: does it block or depend on other issues?
- Suggested order based on priority labels and dependencies
-
Suggest a sprint plan:
- What to finish first (active work)
- What to pick up next (from queued)
- What needs refinement before starting
-
If the user wants to re-prioritize:
- Add/remove labels:
gh issue edit <NUMBER> --add-label "priority:high" - Unassign to defer:
gh issue edit <NUMBER> --remove-assignee @me
- Add/remove labels:
-
If
$ARGUMENTScontains an issue number, fetch its details withgh issue view <NUMBER>and provide a deeper analysis.
Cross-References
- Want to start a task? Run
/develop-full <ISSUE_NUMBER> - Need more context on an issue? Run
/issue <ISSUE_NUMBER> - Quick daily check? Run
/standupinstead
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 · 54 lines · 16 tokens per session scan A ce02d96544a6
sprint-plan is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 464 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.
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.