Borrowing it
Nothing to install: this file belongs to srbryers/slope. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/srbryers/slope/main/.claude/skills/slope-sprint-workflow/SKILL.mdgit 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/skills/srbryers/slope/slope-sprint-workflow)<a href="https://agentmods.dev/skills/srbryers/slope/slope-sprint-workflow"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-sprint-workflow/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.
<a href="https://agentmods.dev/skills/srbryers/slope/slope-sprint-workflow"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-sprint-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00076 | $0.00799 |
| Opus 5 | $0.00038 | $0.00400 |
| Sonnet 5 | $0.00015 | $0.00160 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
slope-sprint-workflow 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 9d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLOPE Sprint Workflow
Sprint execution agent for SLOPE-managed projects. Follow the routine hierarchy precisely — each routine prevents specific failure modes observed across 60+ sprints.
File Map
| File | Purpose |
|---|---|
SKILL.md |
This file — overview and quick reference |
gotchas.md |
Top recurring hazards with prevention steps |
references/routines.md |
Full pre-round, pre-shot, post-shot, post-hole routines |
references/hazard-guide.md |
Hazard types with real sprint examples and prevention |
scripts/sprint-helpers.js |
execute() snippets for scorecard validation, briefing, branch hygiene |
Quick Reference
| Phase | Routine | Key Actions |
|---|---|---|
| Start | Pre-Round | slope now, slope roadmap focus --sprint=N, briefing, verify last scorecard |
| Per-Ticket | Pre-Shot | Select club, check yardage book, scan hazards |
| Per-Ticket | Post-Shot | Score shot, record hazards, push |
| End | Post-Hole | Score hole, validate, review, distill, PR |
Par & Slope
- Par: 1-2 tickets = 3, 3-4 tickets = 4, 5+ tickets = 5
- Slope: Count complexity factors (new infra, multi-package, schema changes, external APIs, concurrent agents)
Club Selection
| Club | Complexity | Examples |
|---|---|---|
driver |
High risk, new territory | New infrastructure, unknown APIs |
long_iron |
Multi-package, significant | Cross-package refactors, schema migrations |
short_iron |
Standard feature work | Well-understood patterns, single package |
wedge |
Small changes | Config updates, docs, minor fixes |
putter |
Trivial | Typos, one-line changes |
Commit Discipline
Commit triggers: each new file, each feature, each migration, each doc update, each bug fix, before context switches, every ~15 minutes, session end.
Push triggers: after each ticket, every 30 minutes, before compaction, session end.
Format: <type>(<ticket>): <imperative summary> — Types: feat, fix, refactor, docs, test, chore, wip
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 81 lines · 76 tokens per session scan A 8f829bccaad5
slope-sprint-workflow is a skill published in the GitHub repository srbryers/slope (6 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 799 once invoked, about $0.0004 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.