performance-optimization-for-langgraph

A set of instructions for improving the speed and cost of LangGraph applications. LangGraph is a framework for building workflows where language-model tasks run as connected steps.

In plain words
What is it for?
Use it when tuning LangGraph workflows with caching, asynchronous execution, or performance and cost monitoring.
Why use it?
It helps identify ways to avoid repeated work, reduce waiting time, run tasks asynchronously, use fewer tokens, and track costs.

Skill for Claude CodeCodex

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

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,121 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.00052 $0.02121
Opus 5 $0.00026 $0.01060
Sonnet 5 $0.00010 $0.00424
Haiku 4.5 $0.00005 $0.00212

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

Security

Grade A, and why

performance-optimization-for-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 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/skills/langgraph-dev-performance-optimization/SKILL.md · 305 lines

How it starts

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

Performance Optimization for LangGraph

Optimize LangGraph workflows through node-level caching, async patterns, and cost monitoring.

Note: Examples in this skill assume a compiled graph instance graph. See the Node-Level Caching section for a complete example of graph creation.

Node-Level Caching with CachePolicy

LangGraph provides node-level caching to avoid redundant computation. Use CachePolicy to configure caching per node.

from langgraph.cache.memory import InMemoryCache
from langgraph.types import CachePolicy
from langgraph.graph import StateGraph
from langchain_anthropic import ChatAnthropic

# Initialize LLM instance (reuse for connection pooling)
llm = ChatAnthropic(model="claude-sonnet-4-5-20250929", max_tokens=1024)

def expensive_llm_node(state: dict) -> dict:
    """Node that makes expensive LLM calls."""
    response = llm.invoke(state["query"])
    return {"response": response}

# Create graph builder
builder = StateGraph(dict)

# Add node with cache policy (TTL in seconds)
builder.add_node(
    "llm_node",
    expensive_llm_node,
    cache_policy=CachePolicy(ttl=3600)  # Cache for 1 hour
)

# Compile graph with cache
graph = builder.compile(cache=InMemoryCache())

# Repeated invocations with same input return cached results
result1 = graph.invoke({"query": "What is Python?"})  # Calls LLM
result2 = graph.invoke({"query": "What is Python?"})  # Returns cached

Custom Cache Keys:

import hashlib
import json

def custom_key_func(input_data: dict) -> str:
    """Generate cache key from specific fields."""
    key_data = {"query": input_data.get("query")}
    serialized = json.dumps(key_data, sort_keys=True)
    return hashlib.md5(serialized.encode(), usedforsecurity=False).hexdigest()

builder.add_node(
    "llm_node",
    expensive_llm_node,
    cache_policy=CachePolicy(ttl=3600, key_func=custom_key_func)
)

Async for Throughput

import asyncio

# Sequential (slow)
def process_queries_sync(queries):
    results = []
    for query in queries:
        result = graph.invoke({"messages": [query]})
        results.append(result)
    return results

# Parallel (fast) with error handling
async def process_queries_async(queries: list[str]) -> list[dict]:
    """Process queries in parallel with error handling."""
    tasks = [graph.ainvoke({"messages": [q]}) for q in queries]
    results = await asyncio.gather(*tasks, return_exceptions=True)
    # Filter out exceptions or handle them as needed
    return [r for r in results if not isinstance(r, Exception)]

Read the full file on GitHub · 305 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 · 305 lines · 52 tokens per session scan A 3154a79a3ed7

Subscribe to this mod's changes

performance-optimization-for-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,121 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.

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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens