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/suraj1235/open-dynamic-workflows/agents-mdgit clone --depth 1 https://github.com/Suraj1235/open-dynamic-workflowsWrote 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/suraj1235/open-dynamic-workflows/agents-md)<a href="https://agentmods.dev/instructions/suraj1235/open-dynamic-workflows/agents-md"><img src="https://agentmods.dev/badge/instructions/suraj1235/open-dynamic-workflows/agents-md.svg" alt="Measured on agentmods" 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 | $0.00247 | $0.00247 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
open-dynamic-workflows 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 4d 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
Open Dynamic Workflows
For generic MCP hosts, Kimi Code, Zed, and zcode-compatible agents, route substantial workflow requests through the ODW MCP server when it is available.
Use ODW when the user says workflow:, ultracode, /deep-research, or asks for broad multi-file work that benefits from planning, parallel agents, verification, or crash-resumable execution.
- Call
odw_healthfirst when uncertain whether the daemon is reachable. - Use
odw_runfor direct execution. Useodw_planfirst when the user asks to review the plan, the task is expensive, or mutation risk is high. - Report the workflow id, topology, agent count, and cost/time estimate instead of redoing the work manually.
- Use
odw_status,odw_result, andodw_listto monitor and summarize running work. - If ODW is unavailable, say exactly what is missing (
odw-daemon startorodw-daemon doctor <agent>) and then fall back to the host agent native planning only if useful.
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.
- 4d ago First seen · 15 lines · 247 tokens per session scan A 95a9267bf4de
open-dynamic-workflows AGENTS.md is an instructions file published in the GitHub repository Suraj1235/open-dynamic-workflows (36 stars, last pushed 1mo ago), licensed MIT. It adds 247 tokens to every session, about $0.0012 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
harness-sdk AGENTS.md
AGENTS.md instructions for strands-agents/harness-sdk, covering agent development guide - strands agents monorepo, context, monorepo layout, where the "why" lives: team/ and writing code.
matryca-plumber AGENTS.md
AGENTS.md instructions for MarcoPorcellato/matryca-plumber, covering agents.md — matryca plumber instruction router, audience map, instruction loading strategy, always-on working agreements and rule and skill routing.
pydantic-ai-todo CLAUDE.md
Instructions for vstorm-co/pydantic-ai-todo, covering claude.md, what this project is, commands, structure and core pattern.
matryca-plumber CLAUDE.md
Claude Code instructions for MarcoPorcellato/matryca-plumber, covering code audit — code intelligence, always do, never do, resources and cli.
tokenjam AGENTS.md
AGENTS.md instructions for Metabuilder-Labs/tokenjam, covering agents.md — tokenjam and quick rules for agents that don't read claude.md.
NEEDLE CLAUDE.md
Claude Code instructions for jedarden/NEEDLE, covering needle project conventions, msrv, module dependency graph, code style and testing.