Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/marcusgoll/Spec-Flownpx agentmods add commands/marcusgoll/spec-flow/implement-epicWrote 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/marcusgoll/spec-flow/implement-epic)<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/implement-epic"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement-epic/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/commands/marcusgoll/spec-flow/implement-epic"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement-epic.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.00019 | $0.02326 |
| Opus 5.5 | $0.00008 | $0.00930 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (96 stars, last pushed 24d ago), licensed MIT. It adds 19 tokens to every session and 2,326 once invoked, about $0.0001 per session on Opus 5.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
sync-linear
Sync current work with Linear ticket status.
end-work
Complete work session with final checklist.
backlog
PitWay: Capture out-of-scope work discovered mid-task, without expanding current scope.
plan
Hierarchical planning entry point — all 11 plan verbs in one command. v3.7.2 consolidates /aura-frog:plan- (10 commands) into a single dispatcher that routes via the plan-orchestrator skill. The legacy plan- aliases still work as thin stubs.
plan-freeze
Manually freeze a plan node, cascading to descendants. Alias for /aura-frog:plan freeze (v3.7.2+).
plan-next
Return and activate the next ready T4 task. Alias for /aura-frog:plan next (v3.7.2+).