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 skills/donovan-yohan/hermes-plugin-dynamic-workflows/dynamic-workflowsnpx skills add donovan-yohan/hermes-plugin-dynamic-workflows --skill dynamic-workflowsgit clone --depth 1 https://github.com/donovan-yohan/hermes-plugin-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/skills/donovan-yohan/hermes-plugin-dynamic-workflows/dynamic-workflows)<a href="https://agentmods.dev/skills/donovan-yohan/hermes-plugin-dynamic-workflows/dynamic-workflows"><img src="https://agentmods.dev/badge/skills/donovan-yohan/hermes-plugin-dynamic-workflows/dynamic-workflows.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.00031 | $0.02717 |
| Opus 5 | $0.00015 | $0.01358 |
| Sonnet 5 | $0.00006 | $0.00543 |
| Haiku 4.5 | $0.00003 | $0.00272 |
Grade A, and why
dynamic-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 3d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamic Workflows Plugin Skill
Use this when operating the hermes-dynamic-workflows plugin itself. It is not the generic fan-out pattern skill. It tells you how to call the plugin tools that ship with this repo.
Plugin-provided skills are explicit-load only. Load this one as:
skill_view(name="hermes-dynamic-workflows:dynamic-workflows")
When to Use
Use this skill when the user asks to:
- validate, run, inspect, pause, resume, stop, or retry a Dynamic Workflows run;
- author or run a workflow-script harness;
- use
agent(...),kanban_agent(...),parallel(...),pipeline(...), orcapability(...)inside a workflow script; - inspect blocked waits, approvals, finalizers, or child-agent state;
- debug the plugin installation or its workflow state stores.
Do not use this for small one-off tool sequences. Just call the normal tools.
Installed Surface
The plugin registers two model-facing tools in the dynamic_workflows toolset:
workflow— validate/run/status/catalog/script operations.workflow_control— operator controls and blocked-wait/status inspection.
The plugin stores state under the active HERMES_HOME by default:
$HERMES_HOME/dynamic-workflows/runs/
$HERMES_HOME/dynamic-workflows/controls/
$HERMES_HOME/dynamic-workflows/script-runs/
$HERMES_HOME/dynamic-workflows/background-runs/
$HERMES_HOME/dynamic-workflows/scripts/
$HERMES_HOME/dynamic-workflows/templates/
Useful overrides:
HERMES_WORKFLOWS_STATE_DIR # run store root; sibling stores live beside it
HERMES_WORKFLOWS_SCRIPT_CATALOG_DIR # saved script harness catalog root
HERMES_WORKFLOWS_CATALOG_DIR # JSON workflow template catalog root
JSON Workflow Definitions
Fast path:
workflow(action="validate", definition={...})
workflow(action="run", definition={...}, inputs={...})
workflow(action="status", run_id="wf_...")
Minimal definition:
{
"version": "1",
"name": "hello",
"policy": {"network": false, "filesystem": false, "max_parallel": 2},
"inputs": {"name": "string"},
"steps": [
{
"kind": "agent",
"id": "greet",
"agent": "hermes.greeter",
"input": {"subject": "$ref:inputs.name"},
"output_schema": {"greeting": "string"}
}
]
}
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.
- 3d ago First seen · 289 lines · 31 tokens per session scan A 2b5dd3544ca4
dynamic-workflows is a skill published in the GitHub repository donovan-yohan/hermes-plugin-dynamic-workflows (2 stars, last pushed 27d ago), licensed MIT. It adds 31 tokens to every session and 2,717 once invoked, about $0.0002 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-31.
Other skills, from other repositories
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.
kanban-worker
Kanban worker lifecycle: claim, work, heartbeat, complete.
kanban-orchestrator
Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically…
kanban-worker
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBANGUIDANCE (from agent/promptbuilder.py); this skill is what you load when you want deeper detail on specific scenarios.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.