Borrowing it
Nothing to install: this file belongs to assisjp/specflow. 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/assisjp/specflow/main/AGENTS.mdgit clone --depth 1 https://github.com/assisjp/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/assisjp/specflow/agents-md)<a href="https://agentmods.dev/instructions/assisjp/specflow/agents-md"><img src="https://agentmods.dev/badge/instructions/assisjp/specflow/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/assisjp/specflow/agents-md"><img src="https://agentmods.dev/badge/instructions/assisjp/specflow/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.01643 | $0.01643 |
| Opus 5.5 | $0.00657 | $0.00657 |
| Sonnet 5.5 | $0.00329 | $0.00329 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
specflow 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 4d 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. AGENTS.md is the canonical source for contributors using either harness. Claude Code loads the repository-only pointer in .claude/rules/repository.md; plugin consumers receive the promoted skills, not these development conventions.
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 four, 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.
- 4d ago Changed · +66 lines · +1,381 tokens per session 61aa834fef90
- 2mo ago First seen · 11 lines · 262 tokens per session scan A 8b9b4fe99838
specflow AGENTS.md is an instructions file published in the GitHub repository assisjp/specflow (17 stars, last pushed yesterday), licensed MIT. It adds 1,643 tokens to every session, about $0.0066 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-08-30.
Other instructions, from other repositories
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).
next.js AGENTS.md
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, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.