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 skills add ccbud/CCBuddy --skill dynamic-workflowsgit clone --depth 1 https://github.com/ccbud/CCBuddyWrote 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/ccbud/ccbuddy/dynamic-workflows)<a href="https://agentmods.dev/skills/ccbud/ccbuddy/dynamic-workflows"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/dynamic-workflows/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/skills/ccbud/ccbuddy/dynamic-workflows"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/dynamic-workflows.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.00092 | $0.21721 |
| Opus 5.5 | $0.00037 | $0.08688 |
| Sonnet 5 | $0.00018 | $0.04344 |
| Haiku 4.5 | $0.00009 | $0.02172 |
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 yesterday.
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 — 1,521 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing dynamic workflows
This skill is the whole authoring contract for CreateWorkflow. The tool descriptions are
short on purpose; the facade the compiler checks against, the rules a script must satisfy and
the fields each tool takes are in §16, and CreateWorkflow, AmendWorkflow, SaveWorkflow
and EvalWorkflowSnippet refuse to run until this skill has been loaded in the session. The
rest is the judgment layer: how many subagents a request deserves, which of them should share
a context, what each one should hand back, and how to keep the run's work from dying with the
run.
Two names collide in this codebase. CreateWorkflow is the dynamic-workflow tool and the
only one this skill is about. The legacy Workflow tool and /expert are a different,
older feature that happens to share the word.
The bar: first-class, expert-level work
A workflow exists to produce first-class, expert-level work — the deliverable a senior practitioner would hand over after doing the job properly, not a faster draft of what one reply could have said. A user who asks for a workflow is paying for that depth, and every choice in this skill serves it: enough subagents to actually cover the ground, fresh eyes on every plan and every draft (§3), an independent confirmation of every finding, deterministic checks wherever a command can decide, and a report that says what was verified, what was not, and what it all means. Depth is measured by what is at stake, not by how many subagents re-read the same work: verification is spent where a wrong claim would cost the user something, and each piece of work gets the one check that decides it, not every check this skill knows. When a shortcut and the expert's way disagree, take the expert's way. Trim the work only when the task is genuinely small, never because thoroughness is inconvenient; trim the checking when a wrong claim costs little or a command has already decided it.
1. Is this the right tool, and how big should it be?
| The request | The tool |
|---|---|
| One thing delegated to one agent | Agent |
| A few independent lookups, nobody reading anybody's answer | Agent, in parallel |
| Anything else the user did not name a workflow for — however many steps or subagents it needs | Agent, or do it yourself |
| The user said "use a workflow" / "使用 workflow" / "用工作流" — any phrasing naming workflow as the means | CreateWorkflow, mandatory, even if Agent would have done or one reply could answer |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 1,521 lines · 92 tokens per session scan A 2664156a460a
dynamic-workflows is a skill published in the GitHub repository ccbud/CCBuddy (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 92 tokens to every session and 21,721 once invoked, about $0.0004 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-09-25.
Other skills, from other repositories
codex-auth-setup
Install or refresh codex-multi-auth for the official Codex CLI, run first login, and verify account health and routing.
example
Example fixture skill for scanner regression coverage.
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.
context-canvas-reflection
Run one bounded trajectory reflection when repeated same-cause failures, contradicted assumptions, real-use failure after local green, material scope drift, a materially unresolved phase boundary, an unapproved authority-sensitive next effect, or user doubt suggests the current path may be wrong. Use Context Canvas…
context-canvas-checkpoint
Maintain an optional session task map and explicit retrievable references in Context Canvas Codex. Use when navigation or long-context offload would materially help with goals, decisions, progress, dependencies, blockers, next steps, exploration summaries, large textual tool results, or selective historical…
cost-tracker
Track LLM API spend per session and task. Estimate token usage across providers. Warn before you blow your budget.