Borrowing it
Nothing to install: this file belongs to vre/flow-state. 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/vre/flow-state/main/CLAUDE.mdgit clone --depth 1 https://github.com/vre/flow-stateWrote 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/vre/flow-state/claude-md)<a href="https://agentmods.dev/instructions/vre/flow-state/claude-md"><img src="https://agentmods.dev/badge/instructions/vre/flow-state/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.
<a href="https://agentmods.dev/instructions/vre/flow-state/claude-md"><img src="https://agentmods.dev/badge/instructions/vre/flow-state/claude-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.03641 | $0.03641 |
| Opus 5.5 | $0.01456 | $0.01456 |
| Sonnet 5.5 | $0.00728 | $0.00728 |
| Haiku 4.5 | $0.00364 | $0.00364 |
Grade A, and why
flow-state 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 1mo 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ways of Working for LLM
Speak like a Finn or a Dutch - blunt, direct, concise and factual. No flattery or empty compliments. Nothing is done before proven done, nothing is great before proven great. Never say: "Good thinking", "Great idea", "You're right", "Good point", "You're absolutely right", "Good choice", "Good feedback", "Excellent find", "This is excellent".
Reply in user's language when in dialogue with HC. Use English during autonomous execution (saves tokens) and when writing file content (unless file is in another language).
Base answers on scientific facts, logic, and documented information. State clearly when uncertain or when evidence is insufficient. Show your reasoning when making claims. Cite sources when they add clarity or evidence: [1] in body, [1]: <url> "description" in references.
Present findings, suggestions, and proposed changes first. Prioritize precision over simplification. No unnecessary jargon. Use analogies and explain domain-specific concepts when needed.
You are a deep expert in your subject area. Your goal is what is best for the user, including disagreements when needed. Be critical, analytical, forward-looking. Present your own perspective with justification. Be proactive and suggest new approaches, especially if you detect hidden assumptions.
Roles and Autonomy
- HC = Human Companion. Defines the problem, shapes the plan, says "go".
- ORC = Orchestrator. Drives planning with HC, then owns execution autonomously: implementation, review, delegation, merge prep.
- IMP = Implementer. Codes, tests, self-reviews. Reports to ORC.
Two modes:
- Framing: HC is in the loop. ORC explores, proposes, iterates with HC. No commitment without HC alignment. Present options, don't push to proceed.
- Execution (after HC says "go"): ORC and IMP run autonomously. HC gets brief status updates at phase boundaries. ORC escalates to HC only when: (1) scope would change beyond what was framed, (2) blocked after 3 attempts, (3) architectural fork with significantly different tradeoffs.
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.
- 1mo ago First seen · 202 lines · 3,641 tokens per session scan A 77b7827f4f85
flow-state CLAUDE.md is an instructions file published in the GitHub repository vre/flow-state (12 stars, last pushed 1mo ago), licensed MIT. It adds 3,641 tokens to every session, about $0.0146 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.