Borrowing it
Nothing to install: this file belongs to T-rav/hydraflow. 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/T-rav/hydraflow/staging/AGENTS.mdgit clone --depth 1 https://github.com/T-rav/hydraflowWrote 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/t-rav/hydraflow/agents-md)<a href="https://agentmods.dev/instructions/t-rav/hydraflow/agents-md"><img src="https://agentmods.dev/badge/instructions/t-rav/hydraflow/agents-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/t-rav/hydraflow/agents-md"><img src="https://agentmods.dev/badge/instructions/t-rav/hydraflow/agents-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.05037 | $0.05037 |
| Opus 5.5 | $0.02015 | $0.02015 |
| Sonnet 5.5 | $0.01007 | $0.01007 |
| Haiku 4.5 | $0.00504 | $0.00504 |
Grade A, and why
hydraflow 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 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Canonical reference for every agent role in HydraFlow. Each section documents:
- Role — what the agent does and its constraints
- Prompt structure — required sections and ordering
- Output contract — exact markers the system parses
- Key rules — non-negotiable constraints
Source of truth for prompt intent. Prompt text lives in the runner files; this document explains why each prompt is structured the way it is.
Agent Runtimes
HydraFlow is runtime-agnostic. The same prompt contracts work with any
agent CLI that can read a prompt from stdin / a flag and write text to stdout.
The output markers (PLAN_START, VERDICT:, SUMMARY:, etc.) are plain text
and impose no tool-specific requirements.
Supported runtimes
| Runtime | CLI invocation | Config key |
|---|---|---|
| Claude Code | claude -p "<prompt>" |
planner_tool = "claude" |
| OpenAI Codex | codex "<prompt>" |
planner_tool = "codex" |
| Pi.dev | pi "<prompt>" |
planner_tool = "pi" |
Each stage (plan, implement, review, HITL) can use a different runtime:
HYDRAFLOW_PLANNER_TOOL=claude
HYDRAFLOW_IMPLEMENT_TOOL=codex
HYDRAFLOW_REVIEW_TOOL=claude
HYDRAFLOW_HITL_TOOL=pi
What the runtime must support
For any runtime to work with HydraFlow:
- Stdin / flag prompt ingestion — the prompt is passed as a positional
argument or
--promptflag. - Filesystem access — the agent must be able to read files in the working directory (read-only for the planner, read-write for others).
- Shell tool access —
make lint,make quality,gitcommands must be executable from within the agent session (for implementer and reviewer). - Plain-text stdout — output markers are parsed from raw stdout/stderr; no structured JSON response format is required.
Output marker stability
The following markers are parsed by HydraFlow's Python code and must not be renamed without a coordinated update to the corresponding runner:
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 · 474 lines · 5,037 tokens per session scan A 8a771462115b
hydraflow AGENTS.md is an instructions file published in the GitHub repository T-rav/hydraflow (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 5,037 tokens to every session, about $0.0201 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-31.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.