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.
git 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/commands/marcusgoll/spec-flow/tasks)<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/tasks"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/tasks/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/tasks"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/tasks.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.07943 |
| Opus 5.5 | $0.00000 | $0.03177 |
| Sonnet 5.5 | $0.00000 | $0.01589 |
| Haiku 4.5 | $0.00000 | $0.00794 |
Grade A, and why
tasks 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,041 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tasks — Task Breakdown Generator (Thin Wrapper)
v11.0 Architecture: This command spawns the isolated
tasks-phase-agentvia Task(). All task breakdown logic runs in isolated context.
Active Feature: !ls -td specs/[0-9]*-* 2>/dev/null | head -1 || echo "none"
Interaction State: !cat specs/*/interaction-state.yaml 2>/dev/null | head -10 || echo "none"
Architecture (v11.0 - Phase Isolation):
/tasks → Task(tasks-phase-agent) → tasks.md with TDD structure
Agent responsibilities:
- Read plan.md and spec.md
- Generate 20-30 tasks with acceptance criteria
- Follow TDD Red-Green-Refactor pattern
- Calculate task sizes (XS/S/M/L)
- Identify dependencies and parallel-safe tasks
Mode detection:
- Epic workflows: Sprint breakdown with dependency graph
- Feature workflows: Tasks organized by user story priority
- UI-first mode (--ui-first): Mockup tasks before implementation
Flags:
--ui-first: Generate HTML mockup tasks first--standard: Standard TDD task generation--no-input: Non-interactive mode for CI/CD
Workflow position: spec → clarify → plan → tasks → implement → optimize → ship
Legacy Context (for agent reference)
<legacy_context>
Current git status: !git status --short | head -10
Current branch: !git branch --show-current
Feature spec exists: Auto-detected (epics//epic-spec.md OR specs//spec.md)
Plan exists: Auto-detected (epics//plan.md OR specs//plan.md) </legacy_context>
Step 0: WORKFLOW DETECTION
Detect workflow using centralized skill (see .claude/skills/workflow-detection/SKILL.md):
- Run detection:
bash .spec-flow/scripts/utils/detect-workflow-paths.sh - Parse JSON: Extract
type,base_dir,slugfrom output - If detection fails (exit code != 0): Use AskUserQuestion fallback
- Set paths:
- Feature:
SPEC_FILE="${BASE_DIR}/${SLUG}/spec.md" - Epic:
SPEC_FILE="${BASE_DIR}/${SLUG}/epic-spec.md" - Common:
PLAN_FILE="${BASE_DIR}/${SLUG}/plan.md",TASKS_FILE="${BASE_DIR}/${SLUG}/tasks.md"
- Feature:
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,041 lines · 0 tokens per session scan A 92767d56d701
tasks is a command published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,943 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-08-30.
Other commands, from other repositories
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
tdd
TDD workflow - red-green-refactor per docs/methodology/tdd.md. Use when asked to '/tdd', 'TDD workflow', 'red-green-refactor', 'test-first development', 'write the failing test first'.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.