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/marcusgoll/spec-flow/implement-epicgit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWhat 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.00019 | $0.02326 |
| Opus 5 | $0.00010 | $0.01163 |
| Sonnet 5 | $0.00004 | $0.00465 |
| Haiku 4.5 | $0.00002 | $0.00233 |
Grade A, and why
implement-epic 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 2d 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement-epic - Parallel Sprint Execution
Workflow position: epic → plan → tasks → implement-epic → optimize → ship
Key principles:
- Layers execute sequentially (dependencies respected)
- Sprints within a layer run in parallel (single message, multiple Task calls)
- Workers implement one feature at a time (Domain Memory pattern)
- Errors classified and handled via error-recovery skill
Epic Directory: !ls -td epics/[0-9]*-* 2>/dev/null | head -1
Sprint Plan: !cat epics/*/sprint-plan.md 2>/dev/null | head -30
Sprint Count: !grep -c "^## Sprint S" epics/*/sprint-plan.md 2>/dev/null || echo "0"
Execution Layers: !bash .spec-flow/scripts/bash/sprint-utils.sh layers "$(ls -td epics/[0-9]*-* 2>/dev/null | head -1)" 2>/dev/null
Auto Mode: !echo "$ARGUMENTS" | grep -q "\-\-auto-mode" && echo "enabled" || echo "disabled"
Step 1: Validate Prerequisites
EPIC_DIR=$(ls -td epics/[0-9]*-* 2>/dev/null | head -1)
if [ -z "$EPIC_DIR" ]; then
echo "ERROR: No epic directory found"
echo "Run /epic first to create an epic"
exit 1
fi
# Validate sprint directories exist
bash .spec-flow/scripts/bash/sprint-utils.sh validate "$EPIC_DIR"
Read sprint-plan.md to understand execution layers:
cat "$EPIC_DIR/sprint-plan.md"
Step 2: Initialize Domain Memory (If Missing)
For each sprint without domain-memory.yaml, initialize it:
for sprint_dir in "$EPIC_DIR/sprints"/*/; do
if [ ! -f "${sprint_dir}/domain-memory.yaml" ]; then
SPRINT_ID=$(basename "$sprint_dir")
echo "Initializing domain memory for $SPRINT_ID..."
# Use initializer agent
Task(subagent_type="initializer", prompt="
Initialize domain memory for sprint.
Sprint directory: ${sprint_dir}
Tasks file: ${sprint_dir}/tasks.md
Workflow type: epic-sprint
")
fi
done
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.
- 2d ago First seen · 315 lines · 19 tokens per session scan A 0474a8bbf004
implement-epic is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 2,326 once invoked, about $0.0001 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-30.
Other commands, from other repositories
backlog
PitWay: Capture out-of-scope work discovered mid-task, without expanding current scope.
project
Unified project management. Handles detection, initialization, configuration, context generation, and environment loading.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
whats-next
Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".
sprint-start
Abre uma sprint — cria a branch, o doc da sprint e o objetivo com DoD. Use quando disser "vamos começar a sprint" ou ao terminar a anterior.
project-start
Inicia o Project Genesis Wizard — do "me fale sobre teu projeto" até o primeiro sprint de código, em 5 fases. Não escreve código.