spec-flow-plugin CLAUDE.md

spec-flow-plugin CLAUDE.md is an instructions file for coding agents from IgnacioMarin402/spec-flow-plugin. It costs 1,804 tokens per session, scanned A, original, MIT.

Working rules for a verification engine that checks whether proposed changes and safeguards really work. They require claims to be backed by executed tests and require checking what a component uniquely provides before removing it.

In plain words
What is it for?
Use them when investigating defects, proposing removals, evaluating alternatives, or proving that a fix and its surrounding checks actually work.
Why use it?
They prevent conclusions based only on reading code and reduce the risk of deleting something whose less-obvious responsibilities are still needed.

Instructions file

Installs and runs on its own, but its text points at files inside the plugin that ships it — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed.

Install

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.

agentmods
npx agentmods add instructions/ignaciomarin402/spec-flow-plugin/claude-md
Clone the repo
git clone --depth 1 https://github.com/IgnacioMarin402/spec-flow-plugin

Wrote 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.

agentmods badge for spec-flow-plugin CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ignaciomarin402/spec-flow-plugin/claude-md.svg)](https://agentmods.dev/instructions/ignaciomarin402/spec-flow-plugin/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/ignaciomarin402/spec-flow-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/ignaciomarin402/spec-flow-plugin/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,804 This file is loaded in full into every session.
When invoked 1,804 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01804 $0.01804
Opus 5 $0.00902 $0.00902
Sonnet 5 $0.00361 $0.00361
Haiku 4.5 $0.00180 $0.00180

Measured today against content hash d140ceb63bf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-flow-plugin 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 today.

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.

CLAUDE.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Working agreements for this repo

This engine exists to close one failure: a check that looks armed and is not. The same standard applies to work done on it.

Verify before you claim, and before you propose

A claim without a run behind it is not a finding. Reading the code is how you form a hypothesis; running it is how you learn whether the hypothesis is true. Every defect worth reporting here was found by executing something — several of them contradicted what the source appeared to say.

Before proposing that something be REMOVED, verify what it uniquely provides — not merely that an alternative exists. This is its own rule because it has its own failure mode: finding one good argument for deletion feels like finishing the investigation, and it is the point at which the investigation has barely started. An alternative covering part of a job is evidence about that part and says nothing about the rest.

The concrete case is worth the whole story, because it ends somewhere surprising.

.spec-flow/skills.md was proposed for deletion because Claude Code already lists every skill's name and description to the model, so the table was "redundant for discovery". That was true and irrelevant: discovery was one of three jobs the table did. Two doc quotes supported removal; nothing was checked that could have contradicted them. The proposal was withdrawn.

And the file was deleted anyway, two days later, for reasons the first proposal never touched. Nothing read it — no script parsed it, and the one check that mentioned it only tested that the file existed — so it could name skills that had been renamed or deleted and nobody would learn. Its three jobs each turned out to have an owner elsewhere: a skill's own description maps the decision, the project's agent frontmatter records what it preloads, and the milestone's Skills: field is the instruction. None of that was known when removal was first proposed.

So the lesson is not "do not remove things". It is that being right about the conclusion is not the same as having verified it, and the first version of this argument would have been indistinguishable from the second to anyone reading only the outcome. What separated them was whether anyone had gone looking for the half that disagreed.

Read the full file on GitHub · 148 lines

Changes

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.

  1. today Changed d140ceb63bf9
  2. 4d ago First seen · 148 lines · 1,804 tokens per session scan A 3a99ab791889

Subscribe to this mod's changes

spec-flow-plugin CLAUDE.md is an instructions file published in the GitHub repository IgnacioMarin402/spec-flow-plugin (2 stars, last pushed 3d ago), licensed MIT. It adds 1,804 tokens to every session, about $0.0090 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-08-31.

Related

Other instructions, from other repositories

evolve-loop AGENTS.md

AGENTS.md instructions for mickeyyaya/evolve-loop, covering agents.md — cross-cli canonical instructions, what evolve-loop is, cross-cli invariants (the universal rules), 1. pipeline ordering is non-negotiable and 4. builder writes only inside its worktree.

mickeyyaya/evolve-loop · 4,503 tokens

dev-team CLAUDE.md

Claude Code instructions for biggora/dev-team, covering dev-team plugin, architecture, available agents, shortcut commands (direct agent dispatch) and report protocol.

biggora/dev-team · 3,376 tokens

user-test CLAUDE.md

Claude Code instructions for cosmos-makers/user-test, covering user test plugin, commands, ut modes, persona state and presets.

cosmos-makers/user-test · 322 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens