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/quintinshaw/pi-dynamic-workflows/workflow-patternsnpx skills add QuintinShaw/pi-dynamic-workflows --skill workflow-patternsgit clone --depth 1 https://github.com/QuintinShaw/pi-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/quintinshaw/pi-dynamic-workflows/workflow-patterns)<a href="https://agentmods.dev/skills/quintinshaw/pi-dynamic-workflows/workflow-patterns"><img src="https://agentmods.dev/badge/skills/quintinshaw/pi-dynamic-workflows/workflow-patterns.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.00108 | $0.00797 |
| Opus 5 | $0.00054 | $0.00398 |
| Sonnet 5 | $0.00022 | $0.00159 |
| Haiku 4.5 | $0.00011 | $0.00080 |
Grade A, and why
workflow-patterns 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Built-in workflow patterns
pi-dynamic-workflows ships 5 curated, tested workflow patterns. Each is also a
slash command (/deep-research, /adversarial-review, /code-review,
/multi-perspective, /codebase-audit), but they are equally reachable from
the workflow tool directly: call it with name set to the pattern name
below and args matching its shape, instead of writing an equivalent script
from scratch. Prefer this over authoring a new script whenever the request
fits one of these shapes — the curated version is already reviewed and tested.
A project or user saved workflow of the same name always takes precedence over a built-in of that name — on the slash command, too.
These 5 names are reachable only at the workflow tool's top-level name
input, not via the in-script await workflow(savedName, childArgs) helper —
that helper resolves saved workflows only. Calling workflow('deep-research')
from inside a script fails as an unknown saved workflow; use the top-level
name input instead.
Patterns
name |
When to reach for it | args |
|---|---|---|
deep-research |
Research a question across the web with cross-checked sources | { question: string, angles?: number, minSupport?: number } — angles (default 4) is the number of distinct search queries; minSupport (default 2) is the minimum distinct sources required for a claim to survive cross-checking |
adversarial-review |
Investigate a task/claim, then cross-check each finding with skeptical reviewers | { task: string, reviewers?: number, threshold?: number } |
code-review |
Multi-angle review of a diff (correctness, reuse, simplification, efficiency, altitude) | { diff: string, diffSource?: string } — get diff yourself first (e.g. git diff, gh pr diff <n>); this path does not fetch it for you |
multi-perspective |
Analyze a topic from several independent perspectives in parallel, then synthesize | { topic: string, perspectives?: string[] } — omit or give fewer than 2 to use the default set (technical, product, security, user experience, maintainability) |
codebase-audit |
Run parallel checks against a codebase scope, then cross-validate and report | { scope: string, checks: 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.
- 5d ago First seen · 52 lines · 108 tokens per session scan A e519ff94d759
workflow-patterns is a skill published in the GitHub repository QuintinShaw/pi-dynamic-workflows (489 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 797 once invoked, about $0.0005 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 skills, from other repositories
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.
tmux-manual-qa
Run a single manual tmux-based QA scenario for the todo continuation feature against the real CLI (./pi-test.sh) in an interactive TUI. Captures scrollback, asserts deterministic pass/fail count markers, and cleans up test fixtures. Use only for the manual-qa milestone features.
merge-upstream
Sync a fork branch with an upstream remote using a history-preserving merge. Use this whenever the user says /merge-upstream, merge upstream, sync upstream, sync fork, or wants upstream changes integrated without rebasing or force-pushing.
gpt-image-gen
MUST read before generating images. Detailed prompt-crafting guide for gpt-image models, covering tool routing (native imagegeneration server tool vs the generateimage tool), prompt structure from subject to background, verbatim text rendering, anti-patterns, and the revisedprompt feedback loop for iteration.
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.