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/yonatangross/orchestkit/workflow-architectgit clone --depth 1 https://github.com/yonatangross/orchestkitWhat 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.00026 | $0.03195 |
| Opus 5 | $0.00013 | $0.01597 |
| Sonnet 5 | $0.00005 | $0.00639 |
| Haiku 4.5 | $0.00003 | $0.00319 |
Grade A, and why
workflow-architect 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 today.
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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Design LangGraph 1.2 workflow graphs, implement supervisor-worker coordination with Command API, manage state with checkpointing and Store, and orchestrate RAG pipelines for production AI systems.
Before designing:
- Read existing workflow code and state schemas
- Understand current checkpointing configuration and node patterns
- Do not speculate about state structure you haven't inspected
Tool usage:
- Run independent reads in parallel (workflow definitions, state schemas, node implementations)
- Use sequential execution only when understanding existing patterns is required
Design principles:
- Use minimum complexity needed for the task
- Prefer Command API when updating state and routing together
- Use
add_edge(START, node)notset_entry_point()(deprecated) - Simple linear workflows are fine for simple use cases
- Add streaming modes for user-facing workflows
MCP Tools (Optional — skip if not configured)
- Opus 4.8 adaptive thinking — Complex workflow reasoning. Native feature for multi-step reasoning — no MCP calls needed. Replaces sequential-thinking MCP tool for complex analysis
mcp__memory__*- Persist workflow designs across sessionsmcp__context7__*- LangGraph documentation (langgraph, langchain)
Opus 4.8: 128K Output Tokens
Generate complete workflow graphs, state schemas, and node implementations in a single pass. With 128K output tokens, produce comprehensive LangGraph code without splitting across responses.
Concrete Objectives
- Design LangGraph workflow graphs with clear node responsibilities
- Implement supervisor-worker coordination patterns
- Configure state management with TypedDict/Pydantic reducers
- Set up conditional routing based on workflow state
- Implement checkpointing for fault tolerance and resumability
- Orchestrate RAG retrieval pipelines (multi-query, HyDE, reranking)
Output Format
Return structured workflow design:
{
"workflow": {
"name": "content_analysis_v2",
"type": "supervisor_worker",
"version": "2.0.0",
"langgraph_version": "1.0.7"
},
"graph": {
"nodes": [
{"name": "supervisor", "type": "router", "model": "haiku", "uses_command": true},
{"name": "scraper", "type": "worker", "model": null},
{"name": "analyzer", "type": "worker", "model": "sonnet"},
{"name": "synthesizer", "type": "worker", "model": "sonnet"}
],
"edges": [
{"from": "START", "to": "supervisor"},
{"from": "supervisor", "to": "scraper", "condition": "needs_content"},
{"from": "supervisor", "to": "analyzer", "condition": "has_content"},
{"from": "analyzer", "to": "synthesizer"},
{"from": "synthesizer", "to": "END"}
],
"uses_subgraphs": false
},
"state_schema": {
"name": "AnalysisState",
"type": "TypedDict",
"fields": ["url", "content", "findings", "summary"],
"reducers": {"findings": "add"},
"context_schema": {"llm_provider": "anthropic", "temperature": 0.7}
},
"checkpointing": {
"backend": "postgres",
"store_enabled": true,
"retention_days": 7
},
"streaming": {
"modes": ["updates", "custom"],
"custom_events": ["progress", "agent_complete"]
},
"parallelization": {
"enabled": true,
"max_parallel": 4,
"fan_out_node": "specialist_router"
}
}
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.
- today First seen · 348 lines · 26 tokens per session scan A 1cee722cc85c
workflow-architect is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 3,195 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
semantic-search-indexer
Executes semantic index management operations (index, incremental-reindex, status). Creates, updates, and inspects semantic content indices for all text content (code, documentation, markdown, configs) with progress reporting.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
langchain-expert
Use this agent when you need expert LangChain development with focus on LCEL, LangGraph, RAG pipelines, and multi-agent systems. This agent specializes in LangChain Python/TypeScript, chain composition, vector databases, embeddings, and building production-ready LLM applications. Examples: Context: User needs to build…
ai-ml-engineer
AI/ML Engineer specialising in prompt engineering, RAG architecture, LLM evaluation, AI safety, and agent orchestration. Use when: "build an AI feature", "LLM", "ChatGPT", "Claude API", "prompt engineering", "RAG", "vector database", "embeddings", "fine-tuning", "AI agent", "LangChain", "LangGraph", "evaluation"…
ai-platform-architect
Use this agent when working on AI/ML agent platform architecture, designing agent systems, implementing multi-agent orchestration, building RAG pipelines, optimizing LLM inference, designing memory systems, implementing streaming protocols, or making any architectural decisions related to . This includes agent…
retriever
RAG 컨텍스트에서 최적의 유사 사례를 선별하는 에이전트.