agentmods.dev

start-sprint

start-sprint is a command for Claude Code from srbryers/slope. It costs 0 tokens per session (936 once invoked), scanned A, original, MIT.

A command that prepares a repository for a SLOPE sprint, a defined unit of tracked development work.

In plain words
What is it for?
Use it before starting sprint work when the project uses SLOPE.
Why use it?
It checks previous sprint records, loads relevant planning context, creates a feature branch, and initializes the new sprint.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: names the ExitPlanMode tool.

not rated 6repo yesterday A scan 0 tokens original MIT

Good fit Use it before starting sprint work when the project uses SLOPE.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/srbryers/slope/start-sprint
View source ↗ srbryers/slope
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.

Clone the repo
git clone --depth 1 https://github.com/srbryers/slope

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 start-sprint

README.md
[![agentmods](https://agentmods.dev/badge/commands/srbryers/slope/start-sprint/github.svg)](https://agentmods.dev/commands/srbryers/slope/start-sprint)
Your own site
<a href="https://agentmods.dev/commands/srbryers/slope/start-sprint"><img src="https://agentmods.dev/badge/commands/srbryers/slope/start-sprint/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 start-sprint

Your own site · 80×15
<a href="https://agentmods.dev/commands/srbryers/slope/start-sprint"><img src="https://agentmods.dev/badge/commands/srbryers/slope/start-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 936 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.00000 $0.00936
Opus 5.5 $0.00000 $0.00374
Sonnet 5.5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00094

Measured 2mo ago against content hash e66e9e8d6d7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

start-sprint 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 2mo 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.

templates/claude-code/commands/start-sprint.md · 104 lines

How it starts

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

Start Sprint — Pre-Sprint Setup and Briefing

Run the complete pre-sprint routine: verify prior sprint hygiene, get briefing, create branch, and initialize sprint state.

Arguments

  • $ARGUMENTS — optional: sprint number (auto-detected if omitted)

Steps

1. Determine sprint number

  • If a number was provided as an argument, use it
  • Otherwise, run slope now and use its active or next sprint; use slope next only if no sprint is reported
  • Treat the sprint number as the current SLOPE work unit. It may be a time-boxed interval or a scope-based agent milestone.

2. Load bounded roadmap context

Run slope roadmap focus --sprint=N for the discovered sprint before loading full roadmap history.

3. Verify prior sprint scorecard

Check that the previous sprint's scorecard exists at docs/retros/sprint-{N-1}.json:

  • If missing, stop and create it first using /post-sprint
  • If it exists, continue
  • Note: the sprint-completion guard also enforces this — PR creation is blocked without a scorecard

4. Branch hygiene

  • Run git branch to check for stale branches from prior sprints
  • If stale branches exist, warn the user
  • Create a new feature branch: feat/sprint-{N}-<theme-slug>

5. Run briefing

Run slope briefing to get:

  • Handicap snapshot (rolling performance stats)
  • Hazard index (recent gotchas by area)
  • Filtered common issues relevant to this sprint's work area
  • Session continuity (any handoffs from prior sessions)

If you know the sprint's work area, add filters:

slope briefing --categories=<area> --keywords=<topic>

6. Start sprint with workflow engine

Run slope sprint run --workflow=sprint-standard --var sprint_id=S{N} to start a workflow-controlled sprint.

This activates the workflow engine which:

  • Controls step ordering (plan → review → implement → validate → score)
  • The workflow-step-gate guard blocks file edits outside of agent_work steps
  • State persists in the store — resume with slope sprint resume if interrupted
  • Skip steps with slope sprint skip if not applicable

Read the full file on GitHub · 104 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. 2mo ago First seen · 104 lines · 0 tokens per session scan A e66e9e8d6d7c

Subscribe to this mod's changes

start-sprint is a command published in the GitHub repository srbryers/slope (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 936 tokens. 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.

Git and workflowProject management
Related

Other commands, from other repositories

project

Manage projects: register repos, inspect, configure per-project settings, and remove.

Untrivial-ai/agent-orchestrator · 0 tokens

land

Resolve and squash merge one named, currently authorized pull request.

gmickel/flow-next · 13 tokens

weekly-summary

Generate weekly work summary from git activity.

gopherguides/gopher-ai · 7 tokens

sync

Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.

ruvnet/ruv-FANN · 0 tokens

claim

Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.

ruvnet/ruv-FANN · 0 tokens

next

Suggest the most likely next workflow action based on current context.

jayvee/aigon · 11 tokens