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 marcusgoll/Spec-Flow --skill epic-sprintsgit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWrote 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/marcusgoll/spec-flow/epic-sprints)<a href="https://agentmods.dev/skills/marcusgoll/spec-flow/epic-sprints"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/epic-sprints/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/marcusgoll/spec-flow/epic-sprints"><img src="https://agentmods.dev/badge/skills/marcusgoll/spec-flow/epic-sprints.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.00000 | $0.01159 |
| Opus 5 | $0.00000 | $0.00580 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
epic-sprints 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 7d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Sprints Skill
Generate sprint breakdown with dependency graph and execution layers for epic workflows.
Purpose
Break down epic plans into parallelizable sprints with dependency analysis, API contract locking, and execution layer optimization.
When to Invoke
- During
/epicStep 4 (Sprint Breakdown phase) - After plan.md is complete and reviewed
- Invokes
/taskscommand with epic context
Sprint Breakdown Process
Invoke /tasks with epic context:
/tasks
The /tasks phase will:
- Read plan.md to understand phases
- Analyze complexity and identify sprint boundaries
- Build dependency graph between sprints
- Lock API contracts (OpenAPI schemas) for parallel work
- Generate sprint-plan.md with execution layers
Sprint Plan Structure
<sprint_plan>
<sprints>
<sprint id="S01" name="auth-backend">
<dependencies></dependencies>
<estimated_hours>16</estimated_hours>
<subsystems>backend, database</subsystems>
<contracts_locked>
<api_contract>contracts/api/auth-v1.yaml</api_contract>
</contracts_locked>
</sprint>
<sprint id="S02" name="auth-frontend">
<dependencies>S01</dependencies>
<estimated_hours>20</estimated_hours>
<subsystems>frontend</subsystems>
</sprint>
<sprint id="S03" name="auth-integration">
<dependencies>S01, S02</dependencies>
<estimated_hours>12</estimated_hours>
<subsystems>backend, frontend</subsystems>
</sprint>
</sprints>
<execution_layers>
<layer num="1">
<sprint_ids>S01</sprint_ids>
<parallelizable>true</parallelizable>
</layer>
<layer num="2">
<sprint_ids>S02</sprint_ids>
<parallelizable>false</parallelizable>
<depends_on_layer>1</depends_on_layer>
</layer>
<layer num="3">
<sprint_ids>S03</sprint_ids>
<parallelizable>false</parallelizable>
<depends_on_layer>2</depends_on_layer>
</layer>
</execution_layers>
</sprint_plan>
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.
- 7d ago First seen · 168 lines · 0 tokens per session scan A 00c73a052658
epic-sprints is a skill published in the GitHub repository marcusgoll/Spec-Flow (92 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,159 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-09-03.
Other skills, from other repositories
worker
Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams.
rule-prd-generator
A rule-based workflow for turning interviews, requirements, feedback, or rough proposals into a formal product requirements document (PRD). A PRD explains what a product should do so business, design, development, testing, and operations teams can review it.
spec-driven-dev
A guide for planning software changes in specification documents before implementation. Spec-Driven Development means proposing, reviewing, implementing, verifying, and archiving a change in defined stages.
requirement-assistant
A guide for writing clear requirements, user stories, and feature specifications. A user story describes a need from a user's point of view and the reason it matters.
team
N coordinated agents on shared task list using tmux-based orchestration.
implement-project
Full-lifecycle project workflow. Takes batched tickets, implements via /implement-batch, runs smoke tests, then executes a comprehensive quality pipeline (refactor, review-arch, review-test, tidy-docs, review-release). Maximizes autonomy with andon cord escape.