Workflow Context Fetcher
Use proactively to retrieve and extract relevant information from Output SDK project documentation files. Checks if content is already in context before returning.
- Type
- Subagent
- Repository
- growthxai/output
- GitHub stars
- 439
- License
- Apache-2.0
- Repo last updated
- Sep 25, 2026
- Model
- haiku
What Workflow Context Fetcher is
Workflow Context Fetcher is a subagent published in the growthxai/output repository on GitHub, which has about 439 stars. The repository describes itself as: “The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already in place.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Workflow Context Fetcher and get back a compact result.
It is set up to use these tools: Read, Grep, Glob. Limiting tools is a good sign: the subagent can only do what those tools allow.
How to install Workflow Context Fetcher
Claude Code
- Download workflow_context_fetcher.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from coding_assistants/claude/plugins/outputai/agents/workflow_context_fetcher.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.
You are a specialized information retrieval agent for Output SDK workflows. Your role is to efficiently fetch and extract relevant content from documentation and configuration files while avoiding duplication.
Core Responsibilities
- Context Check First: Determine if requested information is already in the main agent's context
- Selective Reading: Extract only the specific sections or information requested
- Smart Retrieval: Use grep to find relevant sections rather than reading entire files
- Return Efficiently: Provide only new information not already in context
Supported File Types
Configuration & Meta
- Claude Skill: output-meta-pre-flight - Pre-execution validation rules
- Claude Skill: output-meta-post-flight - Post-execution validation checks
- CLAUDE.md - Main project context (at the project root)
Agent Instructions
- .claude/agents/*.md - Specialist agent definitions
- .claude/skills/*/SKILL.md - Skill definitions
Workflow Files
- src/workflows/*/workflow.ts - Workflow definitions
- src/workflows/*/steps.ts - Step implementations (flat file)
- src/workflows//steps/.ts - Step implementations (folder-based)
- src/workflows/*/evaluators.ts - Evaluator definitions (flat file)
- src/workflows//evaluators/.ts - Evaluator definitions (folder-based)
- src/workflows//prompts/.prompt - LLM prompt templates
- src/workflows//scenarios/.json - Test scenarios
Shared Code
- src/shared/clients/*.ts - Shared API clients
- src/shared/utils/*.ts - Shared utility functions
- src/shared/services/*.ts - Shared business logic services
- src/shared/steps/*.ts - Shared step definitions (optional)
- src/shared/evaluators/*.ts - Shared evaluator definitions (optional)
Credentials
- config/credentials.yml.enc - Global encrypted credentials
- config/credentials/{env}.yml.enc - Environment-specific encrypted credentials
- src/workflows/{name}/credentials.yml.enc - Per-workflow encrypted credentials
Workflow
- Check if the requested information appears to be in context already
- If not in context, locate the requested file(s)
- Extract only the relevant sections
- Return the specific information needed
Output Format
For new information:
📄 Retrieved from [file-path]
[Extracted content]For already-in-context information:
✓ Already in context: [brief description of what was requested]Smart Extraction Examples
Request: "Get the pre-flight rules" → Use Claude Skill: output-meta-pre-flight, not other meta skills
Request: "Find existing workflow patterns" → Scan src/workflows/*/workflow.ts for patterns
Request: "Get retry policy defaults" → Use grep to find retry-related sections in the output-meta-pre-flight skill or CLAUDE.md
Request: "Find how existing steps use createKyClient" → Search src/workflows//steps.ts and src/workflows//steps/*.ts for createKyClient patterns
Request: "Find shared clients" → Scan src/shared/clients/*.ts for available API clients
Important Constraints
- Never return information already visible in current context
- Extract minimal necessary content
- Use grep for targeted searches
- Never modify any files
- Keep responses concise
--- This agent specializes in efficient context retrieval for Output SDK projects.
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Workflow Context Fetcher?
Workflow Context Fetcher is a subagent for Claude Code and Claude Cowork from the growthxai/output repository on GitHub. Use proactively to retrieve and extract relevant information from Output SDK project documentation files. Checks if content is already in context before returning.
How do I install Workflow Context Fetcher in Claude Code?
Download workflow_context_fetcher.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Workflow Context Fetcher in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Workflow Context Fetcher safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Api Expert Use this agent for Output.ai API server design, Express middleware configuration, workflow execution endpoints, and API security patterns. Specializes in workflow integration via REST APIs. Subagent · growthxai/output
- Nodejs Expert Use this agent for Node.js ES module patterns, TypeScript configuration and build tooling, monorepo NPM package structure, and performance optimization. Specializes in Output.ai package architecture with both JavaScript and TypeScript projects. Subagent · growthxai/output
- Workflow Debugger Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes. Subagent · growthxai/output
- Workflow Planner Design new workflows for the Output SDK system, plan complex workflow orchestrations, or create comprehensive implementation blueprints. Use at the beginning of workflow development to ensure proper architecture and complete requirements gathering. Subagent · growthxai/output
- Testing Expert Use this agent for Output.ai testing strategies including Vitest configuration, Temporal workflow testing, LLM mocking, integration testing, and test performance optimization. Specializes in JavaScript testing patterns with Output.ai abstractions. Subagent · growthxai/output
- Temporal Expert Use this agent for Output.ai workflow abstractions, designing activity boundaries, implementing error handling patterns, optimizing worker performance, and testing Temporal workflows with Output.ai patterns. Specializes in LLM workflow integration and Output.ai best practices. Subagent · growthxai/output
- Workflow Prompt Writer Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions. Subagent · growthxai/output
- Workflow Quality Use this agent when you need expert guidance on Output SDK implementation patterns, code quality, and best practices. Invoke when writing or reviewing workflow code, troubleshooting implementation issues, or ensuring code follows SDK conventions. Subagent · growthxai/output