agentmods.dev

sova: Command for Claude Code

.claude/commands/sprint-plan.md

sprint-plan is a command for Claude Code from xsovad06/sova. It costs 16 tokens per session (464 once invoked), scanned A, original, Apache-2.0.

A sprint-planning command for reviewing GitHub Issues, which are tracked work items, assigned to you. It can also inspect a GitHub Projects board, a shared planning board.

In plain words
What is it for?
Use it to estimate issue size, identify dependencies, order work, suggest a sprint plan, and adjust issue labels when requested.
Why use it?
It gathers scattered issue details and helps reveal what is active, queued, unclear, or blocked before you choose sprint work.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is xsovad06/sova's own configuration. It tells Claude Code how to work on sova itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sova configures →

not rated 2repo changed 5d ago A scan 16 tokens original Apache-2.0
View source ↗ xsovad06/sova
Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.claude/commands/sprint-plan.md
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sprint-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/sprint-plan/github.svg)](https://agentmods.dev/commands/xsovad06/sova/sprint-plan)
Your own site
<a href="https://agentmods.dev/commands/xsovad06/sova/sprint-plan"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/sprint-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sprint-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsovad06/sova/sprint-plan"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00464
Opus 5.5 $0.00006 $0.00186
Sonnet 5.5 $0.00003 $0.00093
Haiku 4.5 $0.00002 $0.00046

Measured 5d ago against content hash 81c98024d913, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 5d 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.

.claude/commands/sprint-plan.md · 54 lines

What it actually says

Sprint Planning

Review your assigned GitHub Issues, prioritize them, and manage your sprint queue.

Instructions

  1. Fetch assigned issues:

    gh issue list --assignee @me --state open --limit 50 --json number,title,labels,milestone,updatedAt,body

    If the project uses GitHub Projects, also fetch board state:

    gh project item-list --owner <OWNER> --format json 2>/dev/null || true

  2. 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

  3. 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

  4. Suggest a sprint plan:

    • What to finish first (active work)
    • What to pick up next (from queued)
    • What needs refinement before starting

  5. 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

  6. If $ARGUMENTS contains an issue number, fetch its details with gh 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 /standup instead

Rules

  • NEVER use emojis in any output
Changes

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.

  1. 5d ago Changed 81c98024d913
  2. 2mo ago First seen · 54 lines · 16 tokens per session scan A ce02d96544a6

Subscribe to this mod's changes

sprint-plan is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 464 once invoked, about $0.0001 per session on Opus 5.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.

Code reviewProject managementai-agentsautomationautonomous-developmentclideveloper-tools
Related

Other commands, from other repositories

dashboard

Phase 3 monitoring — System health, execution insights, and velocity analytics.

opensesh/KARIMO · 0 tokens

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.

opensesh/KARIMO · 0 tokens

anchors

List what each requirement tag anchors to (read-only).

raccioly/docguard · 11 tokens

implement-evidence-asks

Read by /implement Phase 1 (D-CMD-REF-HAND). "The grammar below", "the exception grammar above" and "the record above" name sections of this file. Any other "above" means the Phase 1 text before the step that sent you here.

dean0x/devflow · 0 tokens

afe

Evaluate feature - code review or comparison (shortcut for feature-eval).

jayvee/aigon · 17 tokens

aitask-pr-import

Create an aitask from a pull request by analyzing PR data and generating a structured task with implementation plan.

beyondeye/aitasks · 21 tokens