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/medadembha/docflow/agents-mdgit clone --depth 1 https://github.com/MedAdemBHA/docflowWhat 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.00307 | $0.00307 |
| Opus 5 | $0.00153 | $0.00153 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
docflow 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.
What it actually says
Agent Guide
Repo use docflow.
Start here:
- Read
docs/README.md. - Read the summary and latest entry in the newest file under
docs/changelog/. Open older entries only when the task needs deeper history. - Then code.
New feature flow:
- Add/update
product-spec/for WHAT. - Add/update
specs/for HOW. - Add/update
plans/features/for status + feature log. - Append shipped work to current
changelog/(mmm-yy).md.
Route by question:
- WHAT feature do:
docs/product-spec/ - HOW built:
docs/specs/ - WHY chose it:
docs/decisions/ - Rules / conventions:
docs/references/ - Planned / in progress:
docs/plans/ - Bugs / audits / quality:
docs/reviews/ - What shipped:
docs/changelog/
Rules:
- Follow
docs/NAMING.md. - Keep
docs/README.mdupdated. Durable doc go there. changelog/append-only. Add current month if missing. Do not rewrite old months except factual fix.- If work change behavior, architecture, decision, plan, or known issue, update docs.
- Prefer docs before code for behavior, architecture, decisions, roadmap, known issues.
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 · 35 lines · 307 tokens per session scan A ceb1dee8c184
docflow AGENTS.md is an instructions file published in the GitHub repository MedAdemBHA/docflow (41 stars, last pushed 17d ago), licensed MIT. It adds 307 tokens to every session, about $0.0015 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
project-legibility AGENTS.md
Instructions for perhapsspy/project-legibility, covering agents.md and 검증.
OpenDocu AGENTS.md
Instructions for yu2001-s/OpenDocu, covering opendocu agent instructions, command resolution, search rules and useful commands.
docs-to-pdf CLAUDE.md
Instructions for jean-humann/docs-to-pdf, covering claude development guide for docs-to-pdf, project overview, development environment setup, using mise (recommended) and install mise (if not already installed).
core copilot-instructions.md
Instructions for asdecided/core: These decisions are already accepted. Do not re-open or contradict them; ask the AsDecided MCP tools (getartifact, searchartifacts) for the full text before proposing a change that touches one.
slideops CLAUDE.md
Instructions for glukicov/slideops, covering claude.md, what this repository is, commands, the demo deck's citations must still match this repo and the citation mechanism (the core idea).
valuein CLAUDE.md
Claude Code instructions for valuein/valuein, covering claude.md, what this repo is (and isn't), sibling repos — where the actual code lives, commands and with a paid/sp500 token.