Borrowing it
Nothing to install: this file belongs to marcusgoll/Spec-Flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/marcusgoll/Spec-Flow/main/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/marcusgoll/spec-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/marcusgoll/spec-flow/agents-md/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/instructions/marcusgoll/spec-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/marcusgoll/spec-flow/agents-md.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.00488 | $0.00488 |
| Opus 5.5 | $0.00195 | $0.00195 |
| Sonnet 5.5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
Spec-Flow AGENTS.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 2mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Flow Agents
Spec-Flow coordinates multiple coding tools through a single shared canon. Every agent must read the same rules, reuse the same artifacts, and only write in its designated areas.
Shared brain
.spec-flow/holds the canonical workflow docs, repo map, state schemas, memory, and automation scripts.- In consumer projects,
epics/<slug>/state.yamlis the single source of truth for epic phase progress; feature-levelspecs/<feature>/state.yamlis optional and must mirror the epic. - Roadmaps, specs, plans, tasks, and ship notes all inherit the phase order:
spec → clarify → plan → tasks → implement → optimize → preview → ship → finalize.
Tool boundaries
.claude/— Claude Code-only prompts, commands, and hooks. Readable by other tools, but only Claude edits this tree..codex/— Codex CLI-specific prompts, commands, adapters, and skills. Codex writes here; other tools leave it alone.- Additional tool adapters must be labeled explicitly until their source-repo surfaces exist.
- Shared assets may live elsewhere in active repo surfaces such as
docs/,bin/,.github/, and.spec-flow/, but every tool must honor.spec-flow/repo-map.yamland.spec-flow/domains/*.yamlwhen deciding where to add code.
Hard rules
- Never fork new “top-level religions.” Add new integrations under their dedicated folder and mirror the shared canon from
.spec-flow/. - All tools may read
.claude/**for reference, yet non-Claude edits are prohibited. - In consumer projects, epic work begins under
epics/<slug>/; features live inspecs/<feature>/and must link back to their parent epic insidestate.yaml. - When progressing any phase, update the relevant
state.yamland stop at the documented review boundaries (no macro “run everything” flows). - Persistent learnings or roadmap shifts belong in
.spec-flow/memory/and should be reflected in the shared docs before modifying tool-specific trees.
Follow these rules and every agent—Claude, Codex, Cursor, or future additions—will operate from the same source of truth.
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.
- 2mo ago First seen · 35 lines · 488 tokens per session scan A 74bf3ca8934c
Spec-Flow AGENTS.md is an instructions file published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 1mo ago), licensed MIT. It adds 488 tokens to every session, about $0.0020 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-09-03.
Spec-Flow AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Spec-Flow AGENTS.mdmarcusgoll/Spec-Flow | Instructions file | 96 | 1mo ago | MIT | A | 488 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | today | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |