Borrowing it
Nothing to install: this file belongs to cofin/flow. 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/cofin/flow/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/cofin/flowWrote 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/cofin/flow/copilot-instructions)<a href="https://agentmods.dev/instructions/cofin/flow/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/cofin/flow/copilot-instructions/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/cofin/flow/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/cofin/flow/copilot-instructions.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.01151 | $0.01151 |
| Opus 5.5 | $0.00460 | $0.00460 |
| Sonnet 5.5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade C, and why
flow copilot-instructions.md scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- flow-rule-adapter: {"activation":"Repository instructions, custom agents, and Agent Skills activate Flow.","automatic_push":false,"canonical_sha256":"8a6c8792d28a246ac1af833e9efab25af3d21c53921ec6512382194bbf4cb46c" How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Operational Rule
Activation: Repository instructions, custom agents, and Agent Skills activate Flow.
When a repository has .agents/, read its configured root, bundle index, active
spec, authoritative task worksheet, and applicable recursively nested knowledge
before acting. Operational skills resolve only from .agents/skills/.
Route through the flow skill and exactly one lifecycle skill. Refine plans
until every worksheet is executable, follow the selected worksheet without
improvising, and route contradictions through revise/refine. Rewrite revised
worksheets in place in present tense without historical transcripts, and keep
Markdown checklist markers ([x], [~], [ ]) synchronized with task state.
Apply direct Markdown frontmatter state synchronization and reconcile task-first.
Close and archive completed specs on the working branch without waiting for branch
merge; when scope grows beyond the active spec, finish the current spec and open a
follow-up spec via /flow:plan. Before deleting any spec during archive,
curate evidence-backed OKF chapters across nested domain, architecture, pattern,
testing, and gotcha folders (knowledge/index.md).
Write direct, zero-slop prose and code: avoid AI puffery, negative parallelisms,
formulaic transitions, and inline # comments in Python (use docstrings and PEP
585 types). Proactively fix adjacent lint, typing, or dead-code issues in touched
in-scope files and suggest the exact canonical /flow:<action> command next.
Use structured-choice-v1 for unresolved decisions: one decision at a time,
only through a currently allowed compatible native tool or the equivalent
sequential-text fallback. Run correctness review and then the mandatory fresh
quality review before finish/archive.
Commits remain local unless the user explicitly asks for delivery. Never create, move, force-update, or delete Git tags.
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 Changed · +13 lines · +184 tokens per session f27e1ec942f8
- 1mo ago First seen · 46 lines · 967 tokens per session scan C 90d57450f1c2
flow copilot-instructions.md is an instructions file published in the GitHub repository cofin/flow (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,151 tokens to every session, about $0.0046 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.