flow-next: Instructions file for Claude Code

CLAUDE.md

flow-next CLAUDE.md is an instructions file for Claude Code from gmickel/flow-next. It costs 594 tokens per session, scanned A, original, MIT.

Project instructions for flow-next, a workflow plug-in for planning and tracking software work with written specifications, tasks, identifiers, records of completed work, and quality checks.

In plain words
What is it for?
Use them when planning or carrying out software-development tasks in flow-next, including specification work, task tracking, review steps, and automated workflow commands.
Why use it?
They provide the project's shared vocabulary, explain when to use its bundled command-line workflow tool, and show where architecture and process rules are documented.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code.

This is gmickel/flow-next's own configuration. It tells Claude Code how to work on flow-next itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything flow-next configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gmickel/flow-next. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gmickel/flow-next/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/gmickel/flow-next

Made for: Claude Code.

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 flow-next CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gmickel/flow-next/claude-md/github.svg)](https://agentmods.dev/instructions/gmickel/flow-next/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/gmickel/flow-next/claude-md"><img src="https://agentmods.dev/badge/instructions/gmickel/flow-next/claude-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.

agentmods 80×15 button for flow-next CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gmickel/flow-next/claude-md"><img src="https://agentmods.dev/badge/instructions/gmickel/flow-next/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 594 This file is loaded in full into every session.
When invoked 594 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00594 $0.00594
Opus 5.5 $0.00238 $0.00238
Sonnet 5.5 $0.00119 $0.00119
Haiku 4.5 $0.00059 $0.00059

Measured 17d ago against content hash 5023c9713d73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flow-next 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 17d 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.

CLAUDE.md · 62 lines

How it starts

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

Flow-Next Claude Code development entry point

Read the shared development policy before repository work. It owns architecture, source ownership, verification, and delivery rules. This file owns host guidance only; keep common rules in that policy.

Canonical spec scaffold: templates/spec.md. When changing shipped skills, agents, references or platform behaviour, also read adding-skills.md.

Host guidance

On Claude Code, invoke skills by skill id, flow-next:flow-next-<name>; the /flow-next:<name> commands are typed by the user and hidden from the model. Other consumers of this file use their supported native equivalent. Distinguish Claude-native product source examples from the tools available to the current development session.

Flow-Next

This repo tracks implementation specs/tasks through Flow-Next. See repository work and delivery for state, templates, and command discovery. Invoke the selected skill with flow-next:flow-next-<name> on Claude Code; follow its task-specific contract. This is a repo-customized block. Keep maintainer additions outside its markers.

Model routing

These are preferences, not facts about this session's model or available tools. Explicit user routing wins, then this block, agent defaults, and the session model. Planning, judgment, user-facing design, and native workers otherwise inherit the actual session model. Read flowctl usage before model steering.

For a Claude-family writer, the maintainer's preferred tiers are:

reviewer: gpt-6.1-sol at high
implementer: opus-5.5
fast scout: opus-5.5
thinking scout: opus-5.5

Reviews focus on overengineering, slop and YAGNI.

Verify availability through the active harness. If this file is read by an OpenAI-family writer, the reviewer preference is not independent-family review; choose a reachable reviewer from another family through the configured backend.

Read the full file on GitHub · 62 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. 17d ago Changed · +1 lines · +5 tokens per session 5023c9713d73
  2. 19d ago Changed · +1 tokens per session fe57ee74ddc7
  3. 21d ago Changed · +2 lines · +10 tokens per session 331eb46f431c
  4. 22d ago Changed · +2 lines · +31 tokens per session e8c06048c0b0
  5. 1mo ago Changed · +1 lines · +19 tokens per session 3c9c3215e75f
  6. 1mo ago Changed · -161 lines · -7,443 tokens per session 7db42ca8bbae
  7. 1mo ago Changed · -3 tokens per session 89c9dd22b120
  8. 1mo ago Changed · +38 tokens per session 3a70df8483d9
  9. 1mo ago First seen · 217 lines · 7,936 tokens per session scan A b92ad0e0b419

Subscribe to this mod's changes

flow-next CLAUDE.md is an instructions file published in the GitHub repository gmickel/flow-next (711 stars, last pushed today), licensed MIT. It adds 594 tokens to every session, about $0.0024 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.

Related

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

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,159 tokens