workflows

A command that reports the status of open dynamic workflows: running workflows, their phases, agents, and budgets. A workflow is a managed sequence of tasks, and agents are the workers carrying out its parts.

In plain words
What is it for?
Use it to check workflow IDs and statuses, see agent completion counts and current phases, review spending, and diagnose whether the workflow daemon is running.
Why use it?
It gives maintainers one summary of work in progress and resource use. If the local workflow service is unavailable, it explains how to install and start it.

Command

Install

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.

agentmods
npx agentmods add commands/suraj1235/open-dynamic-workflows/workflows
Clone the repo
git clone --depth 1 https://github.com/Suraj1235/open-dynamic-workflows
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 112 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00112
Opus 5 $0.00007 $0.00056
Sonnet 5 $0.00003 $0.00022
Haiku 4.5 $0.00001 $0.00011

Measured 2d ago against content hash fea83aaa62d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflows 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.

.opencode/commands/workflows.md · 5 lines

What it actually says

Use the odw_workflows tool to list all workflows known to the local odw daemon (or plugin state if the daemon is offline), then summarize: id, status, phase, agents completed/total, cost so far. If the daemon is not running, say so and show how to install it (from github.com/Suraj1235/open-dynamic-workflows — clone, npm install, npm run setup) and start it (odw-daemon start).

Changes

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.

  1. 2d ago First seen · 5 lines · 14 tokens per session scan A fea83aaa62d6

Subscribe to this mod's changes

workflows is a command published in the GitHub repository Suraj1235/open-dynamic-workflows (35 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 112 once invoked, about $0.0001 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.