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 agents/growthxai/output/workflow_plannergit clone --depth 1 https://github.com/growthxai/outputWhat 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.00042 | $0.02503 |
| Opus 5 | $0.00021 | $0.01252 |
| Sonnet 5 | $0.00008 | $0.00501 |
| Haiku 4.5 | $0.00004 | $0.00250 |
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 2d 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/http - Credentials management using
@outputai/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.
- Prompt file structure with YAML frontmatter
- Liquid.js templating for dynamic content
- Provider and model configuration
- Few-shot examples and system instructions
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.
- 2d ago First seen · 308 lines · 42 tokens per session scan A be823c70dcc1
workflow-planner is an agent published in the GitHub repository growthxai/output (434 stars, last pushed 4d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,503 once invoked, about $0.0002 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 agents, from other repositories
investigate-error
Investigates React compiler errors to determine the root cause and identify potential mitigation(s). Use this agent when the user asks to 'investigate a bug', 'debug why this fixture errors', 'understand why the compiler is failing', 'find the root cause of a compiler issue', or when they provide a snippet of code and…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
d3-expert
Expert in D3.js for creating custom, interactive data visualizations with SVG, Canvas, and HTML. Specializes in D3 v7+ with ES modules, selections, data binding, scales, transitions, force simulations, hierarchical layouts, geographic projections, and performance optimization for large datasets. Use for any data…
react-expert
Use this agent when you need expert React development with focus on React 19+ features, performance optimization, and modern frontend architecture. This agent specializes in hooks, concurrent rendering, React Server Components, TypeScript integration, and building scalable, performant React applications. Examples…
polynv
Autonomously prepare an invariant-elicitation session — harvest candidate invariants from the contract vocabulary, traces, and snapshots, pre-check each against the machine (HOLDS / counterexample / BOUNDED / ERROR), run the mutation adequacy grade, and return the ranked question list with evidence. The INTERVIEW…
polyviz
Autonomously render Polygraph verification artifacts into a clean, brand-consistent diagram set (SVG, optional PNG) and return where the figures landed. Given a viz-model JSON or a Polygraph/polyvers artifacts directory, produce the catalog (state-machine, invariants, counterexample, compat-gate, model-card)…