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 growthxai/output --skill output-plan-workflowgit clone --depth 1 https://github.com/growthxai/outputWrote 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/growthxai/output/output-plan-workflow)<a href="https://agentmods.dev/skills/growthxai/output/output-plan-workflow"><img src="https://agentmods.dev/badge/skills/growthxai/output/output-plan-workflow.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.1 | $0.00050 | $0.02031 |
| Opus 5 | $0.00025 | $0.01015 |
| Sonnet 5 | $0.00010 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
output-plan-workflow 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 7d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task is to generate a comprehensive Output.ai workflow implementation plan in markdown format.
The plan will be displayed to the user who can then decide what to do with it.
Please respond with only the final version of the plan.
Use the todo tool to track your progress through the plan creation process.
Plan Creation Rules
Overview
Generate detailed specifications for implementation of a new workflow.
Output Path
All plan outputs go to: .outputai/plans/YYYY_MM_DD_<workflow_name>_<task_name>/PLAN.md
<process_flow>
Step 0: Arguments Analysis
Analyze the arguments the user provided:
Ensure they have provided:
- workflow_description: The description of the workflow to be created
- additional_instructions: Additional instructions for the workflow
If not, ask the user for the missing information.
Step 1: Context Gathering
Take the time to gather all the context you need to create a comprehensive plan.
- Read any given files or links
- Find any related workflows in the project
- Read the projects documentation files
Step 2: Requirements Clarification
Clarify scope boundaries and technical considerations by asking numbered questions as needed to ensure clear requirements before proceeding.
<clarification_areas> - in_scope: what is included - out_of_scope: what is excluded (optional) - functionality specifics - UI/UX requirements - integration points <llm_provider> - Ask which LLM provider the user wants to use (anthropic, openai, google-vertex, or amazon-bedrock) - Default to anthropic if the user has no preference - All prompt files in the workflow must use the same provider unless the user explicitly requests otherwise - Record the chosen provider so it flows through to prompt engineering (step 6) and implementation </llm_provider> </clarification_areas>
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.
- 7d ago First seen · 297 lines · 50 tokens per session scan A 3ead1ada7d7d
output-plan-workflow is a skill published in the GitHub repository growthxai/output (435 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,031 once invoked, about $0.0003 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.
agent-browser
Browser automation for testing and verification. Use when you need to interact with web UIs, verify visual changes, fill forms, or capture screenshots.
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
mantis-configure
Configures and validates Mantis pipeline environments, sandbox mechanisms, and AI models. Use to set up workflow.json, auto-detect host capabilities, switch between sandboxes (static-only, gvisor, microsandbox, gce), select AI models, and run fast 1-2s preflight tests. Don't use for scanning source code or running…
develop-ai-functions-example
Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures.