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/hulupeep/specflow/claude-mdgit clone --depth 1 https://github.com/Hulupeep/SpecflowWrote 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/hulupeep/specflow/claude-md)<a href="https://agentmods.dev/instructions/hulupeep/specflow/claude-md"><img src="https://agentmods.dev/badge/instructions/hulupeep/specflow/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.1 | $0.02106 | $0.02106 |
| Opus 5 | $0.01053 | $0.01053 |
| Sonnet 5 | $0.00421 | $0.00421 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
Specflow 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 6d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with the Specflow repository.
Project Context
Repository: Hulupeep/Specflow Project Board: GitHub Issues Board CLI: gh (must be installed and authenticated) Tech Stack: Node.js, JavaScript, Jest Primary Focus: Specflow methodology framework — contracts, agents, hooks, templates
Specflow Rules
Rule 1: No Ticket = No Code
All work requires a GitHub issue before writing any code.
Rule 2: Commits Must Reference an Issue
NEVER run git commit without a #<issue-number> in the message.
If you don't know the issue number, ASK before committing.
# Good
git commit -m "feat: add agent validation (#42)"
# Bad — hooks find nothing, no tests run
git commit -m "feat: add agent validation"
Rule 3: Contracts Are Non-Negotiable
Check docs/contracts/ before modifying protected files.
npm test -- contracts # Must pass
Violation = build fails = PR blocked.
Rule 4: Tests Must Pass Before Closing
npm test # All tests (558+)
npm test -- contracts # Contract tests only
npm test -- hooks # Hook tests only
npm test -- schema # Schema validation only
npm test -- compile # Compiler tests only
Work is NOT complete if tests fail.
Rule 5: Contracts Are YAML, Not Markdown
NEVER write contract content (invariants, forbidden patterns, required patterns) into .md files.
Contracts MUST be YAML files in docs/contracts/:
- Feature contracts:
docs/contracts/feature_*.yml - Journey contracts:
docs/contracts/journey_*.yml - Default contracts:
docs/contracts/*_defaults.yml
Wrong: docs/specflow/my-feature-invariants.md
Right: docs/contracts/feature_my_feature.yml
Contract Locations
| Type | Location |
|---|---|
| Project contracts | docs/contracts/*.yml |
| Template contracts | templates/contracts/*.yml |
| Contract tests | tests/contracts/*.test.js |
| Schema tests | tests/schema/*.test.js |
| Hook tests | tests/hooks/*.test.js |
| Compiler tests | tests/compile/*.test.js |
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.
- 6d ago First seen · 246 lines · 2,106 tokens per session scan A 6908dca8cfb5
Specflow CLAUDE.md is an instructions file published in the GitHub repository Hulupeep/Specflow (25 stars, last pushed 1mo ago), licensed MIT. It adds 2,106 tokens to every session, about $0.0105 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-30.
Other instructions, from other repositories
truecourse CLAUDE.md
Claude Code instructions for truecourse-ai/truecourse, covering truecourse — claude instructions, key files to keep updated, project layout, development commands and storage.
truecourse AGENTS.md
AGENTS.md instructions for truecourse-ai/truecourse, covering truecourse — codex instructions, key files to keep updated, project layout, development commands and rules.
PhpCodeArcheology CLAUDE.md
Instructions for PhpCodeArcheology/PhpCodeArcheology, covering claude.md — phpcodearcheology, project overview, language, tech stack and project structure.
oh-my-mermaid CLAUDE.md
Instructions for oh-my-mermaid/oh-my-mermaid, covering project rules, readme localization, versioning, commits and terminology.
drift copilot-instructions.md
Instructions for mick-gsk/drift, covering drift — verbindliche arbeitsgrundlage für alle agenten, primärmodus bei prompt-engineering, zuerst das richtige primitive wählen, nicht verhandelbare schärferegeln and mindestvertrag für jeden guten prompt.
plan-forge git-workflow.instructions.md
Git workflow and commit conventions — conventional commits, push reminders, version-aware messaging.