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/assisjp/specflow/claude-mdgit clone --depth 1 https://github.com/assisjp/specflowWhat 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.01819 | $0.01819 |
| Opus 5 | $0.00910 | $0.00910 |
| Sonnet 5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specflow — repository conventions
specflow supports Claude Code and Codex from one skill source. Claude Code ships it as a single-plugin marketplace; Codex discovers the same skills directly. These rules keep both integrations consistent as skills are added. IMPORTANT: follow them exactly. AGENTS.md is the Codex entry point and directs Codex here for the full shared rules.
Buckets
Skills live under skills/ in bucket folders:
engineering/— code and codebase workproductivity/— non-code workflow toolsin-progress/— drafts not ready to shipmisc/— kept but not promotedpersonal/— tied to one person's setupdeprecated/— no longer used
engineering/ and productivity/ are the promoted buckets — the plugin ships exactly that set.
What every promoted skill needs
A skill in engineering/ or productivity/ MUST have all three, kept in sync:
- A folder
skills/<bucket>/<name>/containingSKILL.md, where the folder name equals thename:in the frontmatter. - An entry in the top-level
README.md, with the skill name linked to itsSKILL.md, grouped under User-invoked or Model-invoked. - An entry in
.claude-plugin/plugin.json'sskillsarray (./skills/<bucket>/<name>). - An
agents/openai.yamlwith Codex UI metadata. User-invoked skills setpolicy.allow_implicit_invocation: false; model-invoked skills leave it enabled.
Skills in in-progress/, misc/, personal/, and deprecated/ MUST NOT appear in README.md or plugin.json.
Docs pages
Every promoted skill also gets a human-facing page at docs/<bucket>/<name>.md, mirroring the two promoted bucket folders. When you add, rename, or change a promoted skill's behaviour, create or re-sync its docs page. Non-promoted skills get no docs page.
Invocation
Every SKILL.md is either user-invoked or model-invoked. Retain Claude Code's existing disable-model-invocation: true field for user-invoked skills. Mirror it in Codex's agents/openai.yaml policy: allow_implicit_invocation: false is user-invoked (still explicitly available as $skill-name in Codex), while the default true is model-invoked. Keep the shared required frontmatter (name and description) present in every skill; do not remove Claude-specific fields from an existing skill. specflow's skills are user-invoked by default: the flow is deliberate, and each step is chosen, not triggered.
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.
- 2d ago First seen · 77 lines · 1,819 tokens per session scan A 16899103673f
specflow CLAUDE.md is an instructions file published in the GitHub repository assisjp/specflow (17 stars, last pushed 23d ago), licensed MIT. It adds 1,819 tokens to every session, about $0.0091 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
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.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.