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/dvnghiem/flowdeck/agents-mdgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.02686 | $0.02686 |
| Opus 5 | $0.01343 | $0.01343 |
| Sonnet 5 | $0.00537 | $0.00537 |
| Haiku 4.5 | $0.00269 | $0.00269 |
Grade A, and why
FlowDeck 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 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Drop-in operating instructions for coding agents. Read this file before every task.
Working code only. Finish the job. Plausibility is not correctness.
This file follows the AGENTS.md open standard (Linux Foundation / Agentic AI Foundation). Claude Code, Codex, Cursor, Windsurf, Copilot, Aider, Devin, Amp read it natively. For tools that look elsewhere, symlink:
ln -s AGENTS.md CLAUDE.md
ln -s AGENTS.md GEMINI.md
0. Non-negotiables
These rules override everything else in this file when in conflict:
- No flattery, no filler. Skip openers like "Great question", "You're absolutely right", "Excellent idea", "I'd be happy to". Start with the answer or the action.
- Disagree when you disagree. If the user's premise is wrong, say so before doing the work. Agreeing with false premises to be polite is the single worst failure mode in coding agents.
- Never fabricate. Not file paths, not commit hashes, not API names, not test results, not library functions. If you don't know, read the file, run the command, or say "I don't know, let me check."
- Stop when confused. If the task has two plausible interpretations, ask. Do not pick silently and proceed.
- Touch only what you must. Every changed line must trace directly to the user's request. No drive-by refactors, reformatting, or "while I was in there" cleanups.
1. Before writing code
Goal: understand the problem and the codebase before producing a diff.
- State your plan in one or two sentences before editing. For anything non-trivial, produce a numbered list of steps with a verification check for each.
- Read the files you will touch. Read the files that call the files you will touch. Claude Code: use subagents for exploration so the main context stays clean.
- Match existing patterns in the codebase. If the project uses pattern X, use pattern X, even if you'd do it differently in a greenfield repo.
- Surface assumptions out loud: "I'm assuming you want X, Y, Z. If that's wrong, say so." Do not bury assumptions inside the implementation.
- If two approaches exist, present both with tradeoffs. Do not pick one silently. Exception: trivial tasks (typo, rename, log line) where the diff fits in one sentence.
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 · 243 lines · 2,686 tokens per session scan A f3f2a739b3db
FlowDeck AGENTS.md is an instructions file published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 14d ago), licensed MIT. It adds 2,686 tokens to every session, about $0.0134 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
oh-my-opencode-slim AGENTS.md
AGENTS.md instructions for alvinunreal/oh-my-opencode-slim, covering agent coding guidelines, project overview, commands, code style and general rules.
agent-framework copilot-instructions.md
Instructions for microsoft/agent-framework, covering github copilot instructions, repository structure and architectural decision records (adrs).
agent-framework python.instructions.md
Instructions for microsoft/agent-framework: See AGENTS.md for project structure and package documentation. Detailed conventions are in the agent skills under .github/skills/.
open-plan-annotator AGENTS.md
Instructions for ndom91/open-plan-annotator, covering open-plan-annotator: development guide, what this is, architecture, runtime distribution and key files.
vibepod-cli AGENTS.md
Instructions for VibePod/vibepod-cli, covering project agent memory, adding a supported agent, tests and maintaining this file.
NEEDLE AGENTS.md
Instructions for jedarden/NEEDLE, covering needle codex guide, project overview, working safely, rust compatibility and code conventions.