create-workflow

A command that generates a LangGraph StateGraph workflow, a graph of connected steps used to run language-model applications.

In plain words
What is it for?
Use it to create React agents with tool calls, corrective retrieval pipelines, multi-agent supervisors, or custom Python workflows, optionally with tests.
Why use it?
It removes the repetitive setup needed to define workflow state, steps, connections, and starting points.

Command

Install

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.

agentmods
npx agentmods add commands/postindustria-tech/agentic-toolkit/create-workflow
Clone the repo
git clone --depth 1 https://github.com/postindustria-tech/agentic-toolkit
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,060 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.01060
Opus 5 $0.00010 $0.00530
Sonnet 5 $0.00004 $0.00212
Haiku 4.5 $0.00002 $0.00106

Measured yesterday against content hash 8a9d6d97b874, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-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 yesterday.

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.

plugins/langgraph-dev/commands/create-workflow.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create LangGraph Workflow

Generate a complete LangGraph workflow with state schema, nodes, edges, and entry points.

Instructions for Claude

When this command is invoked:

1. Gather Requirements

Use AskUserQuestion to collect:

  • Workflow name (if not provided as argument)
  • Pattern to use (if --pattern not provided):
    • react: ReAct agent with tool calling
    • crag: Corrective RAG pipeline
    • multi-agent: Multi-agent supervisor
    • custom: User defines nodes/edges
  • LLM provider preference (or read from settings)
  • Whether to include tests (default: yes)

2. Read Settings

Read .claude/langgraph-dev.local.md if it exists to get:

  • llm_provider (default: anthropic)
  • llm_model (default: claude-sonnet-4-5)
  • async_by_default (default: true)
  • include_type_hints (default: true)
  • include_docstrings (default: true)

3. Validate Inputs

Check:

  • Workflow name is valid Python identifier
  • Target directory doesn't already exist
  • Pattern is valid (react, crag, multi-agent, custom)

4. Generate Directory Structure

Create:

{workflow_name}/
├── graph.py        # StateGraph definition
├── state.py        # TypedDict state schema
├── nodes.py        # Node implementations
├── __init__.py
├── requirements.txt
└── README.md

If tests requested, also create:

{workflow_name}/tests/
├── __init__.py
├── test_state.py
├── test_nodes.py
└── test_graph.py

5. Generate Code Based on Pattern

For ReAct Pattern:
  • State with messages: Annotated[List[BaseMessage], operator.add]
  • Agent node with LLM + tools
  • Tool node using ToolNode
  • Conditional routing via should_continue
For CRAG Pattern:
  • State with query, documents, relevance_scores, web_search_needed
  • Retrieve node
  • Grade documents node
  • Generate node
  • Web search node
  • Conditional routing based on document quality
For Multi-Agent Pattern:
  • State with messages, next_agent
  • Supervisor node with structured output routing
  • Multiple specialized agent nodes
  • Conditional routing to agents

Read the full file on GitHub · 174 lines

Changes

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.

  1. yesterday First seen · 174 lines · 19 tokens per session scan A 8a9d6d97b874

Subscribe to this mod's changes

create-workflow is a command published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 1,060 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-08-31.