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/agoldian/claudenv/dynamic-workflowsnpx skills add AGoldian/claudenv --skill dynamic-workflowsgit clone --depth 1 https://github.com/AGoldian/claudenvWrote 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/agoldian/claudenv/dynamic-workflows)<a href="https://agentmods.dev/skills/agoldian/claudenv/dynamic-workflows"><img src="https://agentmods.dev/badge/skills/agoldian/claudenv/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.00126 | $0.01127 |
| Opus 5 | $0.00063 | $0.00563 |
| Sonnet 5 | $0.00025 | $0.00225 |
| Haiku 4.5 | $0.00013 | $0.00113 |
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamic workflows
Deterministic multi-agent orchestration via the built-in Workflow tool —
a JavaScript script that fans work out across subagents (agent()),
pipelines it (pipeline()), or barriers on it (parallel()). This skill
decides when orchestration earns its cost and gives the minimal scaffold to
launch one. The Workflow tool's own description carries the full API — lean on
it; don't reproduce it here.
Mode detection (FIRST step every time)
Check the system prompt for the marker Dynamic-workflows mode (loop).
- Marker present → LOOP mode. You are inside
claudenv loop. Orchestrate without pausing, but only for plan items that genuinely split into independent sub-tasks, and keep fan-out narrow (see Cost discipline). The goal is law — never pause to ask "запустить workflow?". - Marker absent → INTERACTIVE mode. Propose a one-line orchestration plan (how many agents, what each does, pipeline vs parallel) and wait for the user before launching.
When to orchestrate (triggers)
Reach for a workflow when the work is wide — many items, each handled the same way, with little cross-talk:
- Review / audit a diff across several dimensions (bugs, perf, security, style), then adversarially verify each finding.
- Migrate / edit a pattern across many files (worktree isolation per agent when they mutate in parallel).
- Research a question over many sources, then synthesize.
- Generate N independent attempts (different angles), judge, synthesize from the winner.
- "Find all X" with a verification pass and loop-until-dry.
When NOT to orchestrate (anti-triggers)
Stay single-threaded — a workflow is pure overhead here:
- A single file, or a change that must happen in strict sequence.
- Trivial edits, renames, formatting.
- Anything one or two plain
Agentcalls already cover — prefer those.
Cost discipline. Multi-agent fan-out costs roughly an order of magnitude
more tokens than single-threaded work (~15×; see claudenv-update-plan.md).
Single-threaded is the default. Orchestrate only when the width is real, and
cap the number of concurrent agents to what the task needs.
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 · 106 lines · 126 tokens per session scan A a55ae847e73a
dynamic-workflows is a skill published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 2mo ago), licensed MIT. It adds 126 tokens to every session and 1,127 once invoked, about $0.0006 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
memory
Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
submit-a-plugin
Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry and icon, and opens the pull request.
secrets
Securely request API keys, access tokens, passwords, webhook secrets, or other credentials and write them to a dotenv file without exposing their values to the agent. Use whenever a task needs a credential that the user must supply.
analyze-bundle
Convert Next.js bundle analyzer data to NDJSON and explore it.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.