agentmods.dev

sprint-init

sprint-init is a command for coding agents from skybao1024/sprint-flow. It costs 9 tokens per session (833 once invoked), scanned B, original, MIT.

A command that starts an iterative development sprint from a PRD, a document describing the product requirements.

In plain words
What is it for?
Use it to initialize the files, workflow, roles, and verification plan needed to begin a sprint.
Why use it?
It gives a coding project a structured starting point instead of leaving the work plan scattered or unclear.

Command

Part of the sprint-flow plugin — 1 skill, 4 commands, 3 agents shipped together

not rated 5 19d ago B scan 9 tokens original MIT
View the source file skybao1024/sprint-flow
Install

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.

agentmods
npx agentmods add commands/skybao1024/sprint-flow/sprint-init
Clone the repo
git clone --depth 1 https://github.com/skybao1024/sprint-flow

Or install sprint-flow, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 3 agents.

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-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/skybao1024/sprint-flow/sprint-init.svg)](https://agentmods.dev/commands/skybao1024/sprint-flow/sprint-init)
Your own site
<a href="https://agentmods.dev/commands/skybao1024/sprint-flow/sprint-init"><img src="https://agentmods.dev/badge/commands/skybao1024/sprint-flow/sprint-init.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 833 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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.00009 $0.00833
Opus 5 $0.00005 $0.00417
Sonnet 5 $0.00002 $0.00167
Haiku 4.5 $0.00001 $0.00083

Measured 5d ago against content hash ec812c602618, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade B, and why

sprint-init scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat ~/.claude/plugins/installed_plugins.json | grep -A 3 '"sprint-flow@sprint-flow-marketplace"' | grep installPath | cut -d'"' -f4
plugins/sprint-flow/commands/sprint-init.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sprint Init - Claude Code Wrapper

You are running Sprint Flow initialization in Claude Code.

This command is host-specific. It owns Claude Code tool use, plugin resource discovery, and Claude-specific adaptation. The detailed workflow quality bar lives in the shared spec.

Arguments: $ARGUMENTS (PRD path, optional)

Step 1: Resolve Plugin Root

Find the installed Sprint Flow plugin root before reading shared specs:

cat ~/.claude/plugins/installed_plugins.json | grep -A 3 '"sprint-flow@sprint-flow-marketplace"' | grep installPath | cut -d'"' -f4

Store the result as PLUGIN_PATH.

If empty, fall back to:

find ~/.claude/plugins -type d -name "sprint-flow" | grep -E "cache.*sprint-flow-marketplace" | head -1

Validate these files exist before continuing:

  • {PLUGIN_PATH}/workflow/init-spec.md
  • {PLUGIN_PATH}/workflow/run-spec.md
  • {PLUGIN_PATH}/workflow/loop-spec.md
  • {PLUGIN_PATH}/workflow/status-spec.md
  • {PLUGIN_PATH}/workflow/done-spec.md
  • {PLUGIN_PATH}/personas/backend-developer.md
  • {PLUGIN_PATH}/agents/sprint-executor.md
  • {PLUGIN_PATH}/templates/verification-plan.md
  • {PLUGIN_PATH}/templates/completion-report-backend.md

If the plugin root or specs cannot be found, stop and report the missing path.

Step 2: Load Shared Init Spec

Read {PLUGIN_PATH}/workflow/init-spec.md and {PLUGIN_PATH}/workflow/loop-spec.md completely.

Apply that shared spec for:

  • PRD discovery and analysis
  • project type detection
  • sprint splitting and classification
  • project-level clarification gate
  • frontend/API context discovery
  • .sprint/config.json
  • .sprint/design-decisions.md
  • .sprint/iteration-plan.md
  • .sprint/handoff-sprint-0.md
  • .sprint/verification-plan-sprint-0.md
  • default verification_loop policy in .sprint/config.json
  • existing workflow handling

Claude Code Adaptation

Use these Claude-specific rules while executing the shared spec:

  • Set active host to claude-code.
  • Use CLAUDE.md as runtime.instruction_file_path when it exists; otherwise leave it empty.
  • Use AskUserQuestion for project-level clarification rounds.
  • Ask batched multiple-choice questions when possible.
  • Write .sprint/project-clarification-audit.md before deciding no project-level questions are needed.
  • Reject no_questions unless every decision-risk candidate has impact, exact evidence provenance, and status; generated plans, handoffs, or design decisions cannot be sole evidence for resolved.
  • Set runtime.capabilities.delegation according to Agent availability.
  • Set runtime.capabilities.interactive_questions to true when AskUserQuestion is available.
  • Do not use Codex paths, Codex skills, AGENTS.md, or Codex structured-question language.

Read the full file on GitHub · 91 lines

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 First seen · 91 lines · 9 tokens per session scan B ec812c602618

Subscribe to this mod's changes

sprint-init is a command published in the GitHub repository skybao1024/sprint-flow (5 stars, last pushed 19d ago), licensed MIT. It adds 9 tokens to every session and 833 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens