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 skills add srbryers/slope --skill slope-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/skills/srbryers/slope/slope-sprint)<a href="https://agentmods.dev/skills/srbryers/slope/slope-sprint"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-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.
<a href="https://agentmods.dev/skills/srbryers/slope/slope-sprint"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-sprint.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.00059 | $0.00455 |
| Opus 5 | $0.00030 | $0.00228 |
| Sonnet 5 | $0.00012 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
slope-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 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.
What it actually says
SLOPE Sprint Workflow
Use these commands from the repository root.
Inspect
- Run
slope nowto discover the active or next sprint and its next action. - Run
slope roadmap focus --sprint=<discovered>before loading full roadmap history. - Run
slope sprint statuswhen operational gate or rollover detail is needed. - Run
slope briefing --sprint=<discovered>before editing. - If the user asks for a roadmap interview or planning input, run
slope roadmap intervieworslope roadmap interview --agent; MCP agents can also searchmodule: "init".
Start Or Claim
- Start a sprint with
slope sprint begin --sprint=<number> --ticket=<issue-or-ticket>. - If the issue is only on GitHub and not in the local roadmap, the command may report a prep lookup miss after creating sprint state and a claim. Treat that as non-blocking if
slope sprint statusshows the claim. - Create a feature branch before code changes.
Work
- Commit after each meaningful feature, file group, migration, or bug fix.
- Push after each ticket and at least every 30 minutes.
- When guards produce warnings, address the warning or record why it is not applicable.
Close
- Run focused tests, then
pnpm run typecheck,pnpm run build, and the relevant full test suite for the change. - Run
slope review recommend. - Add or update
docs/retros/sprint-<number>.jsonanddocs/retros/sprint-<number>-review.md. - Run
slope validate docs/retros/sprint-<number>.json. - Mark gates with
slope sprint gate <gate>only after the evidence exists.
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 · 37 lines · 59 tokens per session scan A b05996f168e0
slope-sprint is a skill published in the GitHub repository srbryers/slope (6 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 455 once invoked, about $0.0003 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.