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 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/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/quintinshaw/pi-dynamic-workflows/workflow-patterns"><img src="https://agentmods.dev/badge/skills/quintinshaw/pi-dynamic-workflows/workflow-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00108 | $0.00797 |
| Opus 5.5 | $0.00043 | $0.00319 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (555 stars, last pushed 19d ago), licensed MIT. It adds 108 tokens to every session and 797 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-08-30.
Other skills, from other repositories
gpt-image-gen
MUST read before generating images. Prompt-crafting guide for gpt-image-2.5 covering tool routing (native imagegeneration server tool vs the generateimage tool), model and quality selection, prompt structure, exact text rendering, reference-image editing, transparent assets, output formats, and multi-turn refinement.
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.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-primitive-check
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.