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-conditional-routingnpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-conditional-routinggit 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.00067 | $0.04886 |
| Opus 5 | $0.00034 | $0.02443 |
| Sonnet 5 | $0.00013 | $0.00977 |
| Haiku 4.5 | $0.00007 | $0.00489 |
Grade A, and why
conditional-routing-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 — 679 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conditional Routing in LangGraph
Purpose
Conditional routing enables LangGraph workflows to make dynamic decisions about execution paths based on state values. This transforms static pipelines into adaptive agentic systems that respond intelligently to runtime conditions.
When to Use This Skill
Use this skill when workflows need to:
- Branch execution based on confidence scores or quality metrics
- Route to different nodes based on classification results
- Implement retry logic with conditional loops
- Handle success/failure paths differently
- Create adaptive multi-path workflows
- Combine state updates with routing decisions (Command API)
- Implement map-reduce parallel workflows (Send API)
Required Imports
from typing import Literal, TypedDict, Annotated, Sequence, Callable, Any
from collections.abc import Hashable # For type annotations in path functions
from langgraph.graph import StateGraph, START, END
from langgraph.types import Send, Command
import operator # For reducer functions in parallel execution
Note: The Command API was released December 2024. The Send API has been available since LangGraph 0.2.0+. LangGraph v1.0 was released October 2025 as a stability-focused release. All examples are tested with LangGraph 1.0.x and remain compatible with future 1.x releases. Check PyPI for the latest version.
Convention: Throughout this skill, examples use workflow as the variable name for the StateGraph instance. Create it with: workflow = StateGraph(YourStateClass).
Core Concepts
Conditional Edges
Unlike direct edges (add_edge), conditional edges use functions to determine the next node:
from typing import Literal
def router(state: State) -> Literal["high_confidence_path", "low_confidence_path"]:
"""Returns name of next node based on state."""
if state["confidence"] > 0.8:
return "high_confidence_path"
return "low_confidence_path"
workflow.add_conditional_edges(
"classify",
router,
{
"high_confidence_path": "respond",
"low_confidence_path": "clarify"
}
)
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 · 679 lines · 67 tokens per session scan A 6e5a5ea1de08
conditional-routing-in-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 4,886 once invoked, about $0.0003 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.