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 instructions/marcusgoll/spec-flow/claude-mdgit 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/instructions/marcusgoll/spec-flow/claude-md)<a href="https://agentmods.dev/instructions/marcusgoll/spec-flow/claude-md"><img src="https://agentmods.dev/badge/instructions/marcusgoll/spec-flow/claude-md.svg" alt="Measured on agentmods" 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 | $0.04317 | $0.04317 |
| Opus 5 | $0.02159 | $0.02159 |
| Sonnet 5 | $0.00863 | $0.00863 |
| Haiku 4.5 | $0.00432 | $0.00432 |
Grade A, and why
Spec-Flow CLAUDE.md 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 yesterday.
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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Spec-Flow Workflow Kit: Slash commands transform product ideas into production releases via spec-driven development.
WHAT This Is
Spec-Flow is a workflow toolkit for Claude Code that automates the entire software development lifecycle through slash commands. It guides features and epics from specification through planning, implementation, and deployment with built-in quality gates.
All workflow artifacts live in specs/ (features) or epics/ (complex work). The hierarchical CLAUDE.md system provides progressive disclosure - this file contains essential instructions, while detailed documentation loads on-demand from docs/references/.
WHY This Approach Works
- LLMs are stateless — This file onboards Claude consistently each conversation
- Progressive disclosure — Essential instructions here; deep dives in
docs/references/ - Deterministic validation — Scripts handle quality gates; Claude handles creative work
- Hierarchical context — Root → Project → Feature CLAUDE.md (74-80% token reduction)
HOW To Use It
Quick Start
Feature (single subsystem, <16h):
/feature "desc" → /plan → /tasks → /implement → /optimize → /ship
Epic (multiple subsystems, >16h):
/epic "goal" → /plan → /tasks → /implement-epic → /optimize → /ship → /finalize
Resume work: /feature continue or /epic continue
Essential Commands (30 total)
| Command | Purpose |
|---|---|
/feature "name" |
Start single-subsystem feature |
/epic "goal" |
Start multi-sprint complex work |
/quick "desc" |
Quick fix (<100 LOC) |
/plan |
Generate implementation design |
/tasks |
Create TDD task breakdown |
/implement |
Execute tasks with TDD |
/implement-epic |
Parallel sprint execution for epics |
/optimize |
Run quality gates |
/ship |
Deploy (--staging, --prod, status, budget) |
/help |
Context-aware guidance |
Project Setup: /init, /init --preferences, /init --tokens, /roadmap, /prototype, /constitution
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.
- yesterday First seen · 490 lines · 4,317 tokens per session scan A 6fe1e1099a1c
Spec-Flow CLAUDE.md is an instructions file published in the GitHub repository marcusgoll/Spec-Flow (92 stars, last pushed 4mo ago), licensed MIT. It adds 4,317 tokens to every session, about $0.0216 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-09-03.
Other instructions, from other repositories
ralph CLAUDE.md
Claude Code instructions for SantanderAI/ralph, covering ralph — instrucciones del proyecto and paridad bash ↔ powershell (importante).
claude-code-templates CLAUDE.md
Claude Code instructions for Justdvp/claude-code-templates, covering claude.md, project overview, development commands, package management and application commands.
codexspec CLAUDE.md
Claude Code instructions for Zts0hg/codexspec, covering claude.md - codexspec development guide, project overview, purpose, technology stack and architecture.
anchorlaw AGENTS.md
AGENTS.md instructions for unknowbug/anchorlaw, covering anchorlaw 项目 agents.md（项目级常驻指令）, 〇、开始工作前（每个 session 必做）, 一、项目定位（一句话）, 二、主工作流（judge 驱动流水线，v0.11） and 三、技能与宿主入口.
ccmux AGENTS.md
Instructions for max-listov/ccmux: Read CLAUDE.md in this repository root before making any change. It is the single source of truth for working here — repository conventions, what must never be published, the order in which work is finished, committed and released, and the runtime rules (Bun, never Node/npm).
claude-code-statusline AGENTS.md
Instructions for rz1989s/claude-code-statusline, covering claude-code-statusline, project status, essential commands, configuration testing via env overrides and cache management.