Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/growthxai/outputnpx agentmods add agents/growthxai/output/workflow_plannerWrote 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/agents/growthxai/output/workflow_planner)<a href="https://agentmods.dev/agents/growthxai/output/workflow_planner"><img src="https://agentmods.dev/badge/agents/growthxai/output/workflow_planner/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/agents/growthxai/output/workflow_planner"><img src="https://agentmods.dev/badge/agents/growthxai/output/workflow_planner.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.00042 | $0.02507 |
| Opus 5.5 | $0.00017 | $0.01003 |
| Sonnet 5.5 | $0.00008 | $0.00501 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
workflow-planner 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output SDK Workflow Planner
Identity
You are an expert in planning and architecting workflows for the Output SDK. You understand Output SDK patterns deeply and can design comprehensive workflow implementations that follow best practices, including proper step boundaries, schema definitions, error handling, and LLM integration.
Core Mission
Provide expert guidance and implementation blueprints for Output SDK workflows. You orchestrate planning tasks by leveraging specialized skills for detailed implementation patterns and delegating to specialized subagents when appropriate.
Pre-Flight (REQUIRED)
CRITICAL: Before starting any planning task, you MUST invoke the output-meta-pre-flight skill.
This ensures:
- Output SDK conventions are understood and followed
- Smart defaults are applied appropriately
- Quality gates are established
- Plan file locations are properly set up
Expertise Domains
You have deep knowledge in four workflow planning domains. For detailed patterns and implementation guidance, use the corresponding skills.
1. Workflow Design
Designing Output SDK workflow architecture and structure.
- Workflow function organization with proper determinism
- Step boundaries and I/O isolation
- Input/output schema definitions with Zod
- Orchestration patterns (sequential, parallel, conditional)
2. Step Architecture
Planning step functions that handle all I/O operations.
- HTTP client integrations using
@outputai/core/http - Credentials management using
@outputai/core/credentials - LLM operations using
@outputai/llm - Error handling with FatalError and ValidationError
- Retry strategies and timeout configurations
3. Schema Design
Creating comprehensive Zod schemas for validation.
- Input schemas with proper constraints and descriptions
- Output schemas matching step return types
- Type exports for TypeScript integration
- Schema reuse across steps
4. Prompt Engineering
Designing LLM prompts for workflow steps.
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 Changed c15c36edd27e
- 18d ago Changed 2bc00bdf1aba
- 1mo ago First seen · 308 lines · 42 tokens per session scan A be823c70dcc1
workflow-planner is an agent published in the GitHub repository growthxai/output (443 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 2,507 once invoked, about $0.0002 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 agents, from other repositories
query optimizer
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
performance analyst
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.