subgraphs-and-composition-in-langgraph

subgraphs-and-composition-in-langgraph is a skill for Claude Code, Codex from postindustria-tech/agentic-toolkit. It costs 90 tokens per session (2,572 once invoked), scanned A, original, MIT.

Guidance for building LangGraph workflows from smaller graphs that can be reused, tested separately, and combined into larger applications. LangGraph is a framework for arranging AI or software steps as connected graphs.

In plain words
What is it for?
Use it when creating nested graphs, reusable workflow components, parent-and-child state mappings, modular multi-agent systems, or graph factories in LangGraph 1.x.
Why use it?
It helps organise complex workflows and control how information moves between a larger workflow and its smaller parts. This can make multi-agent applications easier to divide between components or team members.

Skill for Claude CodeCodex

Part of the langgraph-dev plugin — 21 skills, 4 commands, 1 agent shipped together

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 skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-composition
Any agent
npx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-subgraphs-and-composition
Clone the repo
git clone --depth 1 https://github.com/postindustria-tech/agentic-toolkit

Made for: Claude Code, Codex.

Or install langgraph-dev, the plugin that ships this one along with the rest of its 21 skills, 4 commands, 1 agent.

Wrote 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.

agentmods badge for subgraphs-and-composition-in-langgraph

README.md
[![agentmods](https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-composition.svg)](https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-composition)
Your own site
<a href="https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-composition"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-composition.svg" alt="Measured on agentmods" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,572 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.00090 $0.02572
Opus 5 $0.00045 $0.01286
Sonnet 5 $0.00018 $0.00514
Haiku 4.5 $0.00009 $0.00257

Measured 4d ago against content hash 75ba99e28c67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

subgraphs-and-composition-in-langgraph 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.

The scan reads SKILL.md. This mod also ships 6 executable files (examples/01_basic_subgraph_shared_state.py, examples/02_subgraph_different_schema.py, examples/03_multi_level_nesting.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/skills/langgraph-dev-subgraphs-and-composition/SKILL.md · 310 lines

How it starts

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

Subgraphs and Composition in LangGraph

Purpose

This skill provides guidance on building modular LangGraph applications through subgraph composition. Subgraphs enable you to create reusable, independently testable workflow components that can be composed into complex multi-agent systems with clear boundaries and explicit state contracts.

Compatibility

This skill is compatible with LangGraph 1.x (tested with v1.0.6, January 2026).

When to Use This Skill

Use this skill when:

  • Building large multi-agent systems that benefit from modular decomposition
  • Creating reusable workflow components across multiple applications
  • Managing complex state relationships between parent and child workflows
  • Isolating specific functionality for independent testing and optimization
  • Scaling teams working on different parts of a workflow system
  • Implementing hierarchical agent architectures with specialized sub-agents

Core Concepts

1. Subgraph as Node

A compiled StateGraph can be added as a node to another graph. Compiled graphs are callable, making them valid node functions:

from langgraph.graph import StateGraph, START, END, MessagesState

def create_sentiment_subgraph():
    subgraph = StateGraph(MessagesState)
    subgraph.add_node("analyze", analyze_sentiment)
    subgraph.add_edge(START, "analyze")
    subgraph.add_edge("analyze", END)
    return subgraph.compile()

# Add compiled subgraph as a node
chatbot = StateGraph(MessagesState)
chatbot.add_node("sentiment", create_sentiment_subgraph())
chatbot.add_edge(START, "sentiment")
chatbot.add_edge("sentiment", "respond")
chatbot.add_edge("respond", END)

2. Shared State Schema Communication

Parent and child graphs can share the same state schema for seamless communication:

from langgraph.graph import MessagesState
from langchain_core.messages import SystemMessage

def analyze_sentiment(state: MessagesState) -> dict:
    last_message = state["messages"][-1].content.lower()
    sentiment = "positive" if "happy" in last_message else "neutral"
    return {"messages": [SystemMessage(content=f"[Sentiment: {sentiment}]")]}

# Both parent and child use MessagesState - no transformation needed
subgraph = StateGraph(MessagesState)
subgraph.add_node("analyze", analyze_sentiment)

parent = StateGraph(MessagesState)
parent.add_node("sentiment", subgraph.compile())  # Direct usage

Read the full file on GitHub · 310 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. 4d ago First seen · 310 lines · 90 tokens per session scan A 75ba99e28c67

Subscribe to this mod's changes

subgraphs-and-composition-in-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 2,572 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens