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 skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-compositionnpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-subgraphs-and-compositiongit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWrote 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/skills/postindustria-tech/agentic-toolkit/langgraph-dev-subgraphs-and-composition)<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>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.00090 | $0.02572 |
| Opus 5 | $0.00045 | $0.01286 |
| Sonnet 5 | $0.00018 | $0.00514 |
| Haiku 4.5 | $0.00009 | $0.00257 |
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.
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 — 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
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .gitignore 10 B
- examples/01_basic_subgraph_shared_state.py 5.6 KB runs code
- examples/02_subgraph_different_schema.py 6.9 KB runs code
- examples/03_multi_level_nesting.py 8.0 KB runs code
- examples/04_graph_factory_pattern.py 9.6 KB runs code
- examples/05_complete_support_system.py 11 KB runs code
- examples/06_order_processing_validation.py 16 KB runs code
- examples/README.md 12 KB
- references/best-practices.md 19 KB
- references/complete-examples.md 8.8 KB
- references/component-library-design.md 33 KB
- references/core-patterns.md 22 KB
- references/state-mapping-patterns.md 29 KB
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 · 310 lines · 90 tokens per session scan A 75ba99e28c67
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…