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/srbryers/slope/start-sprintgit clone --depth 1 https://github.com/srbryers/slopeWrote 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.
[](https://agentmods.dev/commands/srbryers/slope/start-sprint)<a href="https://agentmods.dev/commands/srbryers/slope/start-sprint"><img src="https://agentmods.dev/badge/commands/srbryers/slope/start-sprint.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00936 |
| Opus 5 | $0.00000 | $0.00468 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00094 |
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 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.
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 nowand use its active or next sprint; useslope nextonly 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 branchto 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-gateguard blocks file edits outside ofagent_worksteps - State persists in the store — resume with
slope sprint resumeif interrupted - Skip steps with
slope sprint skipif not applicable
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.
- 5d ago First seen · 104 lines · 0 tokens per session scan A e66e9e8d6d7c
start-sprint is a command published in the GitHub repository srbryers/slope (6 stars, last pushed today), 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.