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_context_fetchergit 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/agents/growthxai/output/workflow_context_fetcher)<a href="https://agentmods.dev/agents/growthxai/output/workflow_context_fetcher"><img src="https://agentmods.dev/badge/agents/growthxai/output/workflow_context_fetcher.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 | $0.00030 | $0.00813 |
| Opus 5 | $0.00015 | $0.00407 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
workflow-context-fetcher 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output SDK Context Fetcher Agent
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 definitionssrc/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 templatessrc/workflows/*/scenarios/*.json- Test scenarios
Shared Code
src/shared/clients/*.ts- Shared API clientssrc/shared/utils/*.ts- Shared utility functionssrc/shared/services/*.ts- Shared business logic servicessrc/shared/steps/*.ts- Shared step definitions (optional)src/shared/evaluators/*.ts- Shared evaluator definitions (optional)
Credentials
config/credentials.yml.enc- Global encrypted credentialsconfig/credentials/{env}.yml.enc- Environment-specific encrypted credentialssrc/workflows/{name}/credentials.yml.enc- Per-workflow encrypted credentials
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.
- 4d ago First seen · 100 lines · 30 tokens per session scan A 05f4f859f22e
workflow-context-fetcher is an agent published in the GitHub repository growthxai/output (435 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 813 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
reviewer
Code review specialist for quality/security analysis.
memory
LangGraph supports two types of memory essential for building conversational agents.
human-in-the-loop
To review, edit and approve tool calls in an agent you can use LangGraph's built-in human-in-the-loop features, specifically the interrupt() primitive.
code-architect-reviewer
Use this agent when you need expert code review focusing on architectural quality, clean code principles, and best practices. Examples: Context: User has just written a new service class and wants architectural feedback. user: 'I just implemented a user authentication service. Can you review it?' assistant: 'I'll use…
librarian
Researches external libraries and APIs by reading source code. Returns definitive, source-verified answers.
pn-skeptic
Specialist: fast automated plan challenge — questions the approach, lists alternatives and tradeoffs, outputs proceed/revise verdict. Use for a single-pass review. For interactive Socratic dialogue, use pn-grill instead.