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/implementWrote 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)<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/implement"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement/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"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement.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.00020 | $0.07858 |
| Opus 5.5 | $0.00008 | $0.03143 |
| Sonnet 5.5 | $0.00004 | $0.01572 |
| Haiku 4.5 | $0.00002 | $0.00786 |
Grade A, and why
implement 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 — 1,167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement — Task Execution with TDD
Workflow Detection: Auto-detected via workspace files, branch pattern, or state.yaml
Current Branch: !git branch --show-current 2>/dev/null || echo "none"
Feature Directory: !python .spec-flow/scripts/spec-cli.py check-prereqs --json --paths-only 2>/dev/null | jq -r '.FEATURE_DIR'
Pending Tasks: Auto-detected from ${BASE_DIR}/*/tasks.md
Completed Tasks: Auto-detected from ${BASE_DIR}/*/tasks.md
Git Status: !git status --short 2>/dev/null || echo "clean"
Mockup Approval Status (if UI-first): Auto-detected from ${BASE_DIR}/*/state.yaml
Implementation Artifacts (after script execution):
- @${BASE_DIR}/*/tasks.md (updated with completed tasks)
- @${BASE_DIR}/*/CLAUDE.md (living documentation)
- @design/systems/ui-inventory.md (if UI components created)
- @design/systems/approved-patterns.md (if patterns extracted)
Implementation workflow:
- Parse and group tasks from tasks.md by domain and TDD phase
- Execute tasks directly using specialist agents (backend-dev, frontend-dev, etc.)
- Track completion via tasks.md checkbox and NOTES.md updates
- Update living documentation (UI inventory, approved patterns)
- Run full test suite verification
- Present results with next action recommendation
Key principles:
- Test-Driven Development: Red (failing test) → Green (passing) → Refactor (improve)
- Parallel execution: Group independent tasks by domain, speedup bounded by dependencies
- Anti-duplication: Use mgrep for semantic search before creating new implementations
- Pattern following: Apply plan.md recommended patterns consistently
- Atomic commits: One commit per task with descriptive message
Workflow position: spec → clarify → plan → tasks → implement → optimize → preview → ship
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 · 1,167 lines · 20 tokens per session scan A 041ab2e166ec
implement is a command published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 22d ago), licensed MIT. It adds 20 tokens to every session and 7,858 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
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
build
Invoke the agent-skills:incremental-implementation skill alongside agent-skills:test-driven-development.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
implement-revalidate
Read by /implement when the user asks to re-validate (D-CMD-REF-HAND).
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.