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-graph-constructionnpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-graph-constructiongit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.00075 | $0.03160 |
| Opus 5 | $0.00037 | $0.01580 |
| Sonnet 5 | $0.00015 | $0.00632 |
| Haiku 4.5 | $0.00007 | $0.00316 |
Grade A, and why
graph-construction-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 2d 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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graph Construction in LangGraph
Purpose
This skill provides guidance on constructing LangGraph workflows using StateGraph. Graph construction transforms isolated node functions into orchestrated workflows with explicit control flow, enabling complex multi-step agentic systems.
Compatibility
This skill is compatible with LangGraph 1.x (tested with v1.0.5, December 2025).
Feature-specific version requirements:
interrupt()function: requires LangGraph >= 0.2.31add_sequence()method: requires LangGraph >= 0.2.46
When to Use This Skill
Use this skill when:
- Creating a new LangGraph workflow from scratch
- Adding nodes or edges to existing graphs
- Defining entry points and exit conditions
- Setting up conditional routing between nodes
- Compiling and visualizing graph structures
- Troubleshooting graph connectivity issues
Core Concepts
StateGraph Basics
StateGraph is the foundation of LangGraph workflows:
from langgraph.graph import StateGraph, START, END
from typing import TypedDict # Use typing_extensions.TypedDict for Python 3.9
class State(TypedDict):
messages: list
step: str
# Create graph with state schema
workflow = StateGraph(State)
Using MessagesState for Chat Applications
For chat-based applications, LangGraph provides a built-in MessagesState with automatic message management:
from langgraph.graph import StateGraph, MessagesState, START, END
# MessagesState provides a 'messages' field with add_messages reducer
workflow = StateGraph(MessagesState)
def chat_node(state: MessagesState) -> dict:
# Access messages from state
last_message = state["messages"][-1]
response = generate_response(last_message) # Your LLM call here
return {"messages": [response]}
workflow.add_node("chat", chat_node)
workflow.add_edge(START, "chat")
workflow.add_edge("chat", END)
MessagesState automatically handles message deduplication and updates based on message IDs.
Adding Nodes
What ships with it
7 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_minimal_graph.py 4.2 KB runs code
- examples/02_conditional_routing.py 7.3 KB runs code
- examples/03_graph_with_checkpoints.py 6.4 KB runs code
- examples/04_complete_workflow.py 8.6 KB runs code
- references/advanced-patterns.md 14 KB
- references/performance-and-checkpoints.md 15 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.
- 2d ago First seen · 549 lines · 75 tokens per session scan A 2815c01d2918
graph-construction-in-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 3,160 once invoked, about $0.0004 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.