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-error-recoverynpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-error-recoverygit 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-error-recovery)<a href="https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery.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.00061 | $0.04053 |
| Opus 5 | $0.00030 | $0.02027 |
| Sonnet 5 | $0.00012 | $0.00811 |
| Haiku 4.5 | $0.00006 | $0.00405 |
Grade A, and why
error-recovery-in-langgraph scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Example: return requests.get(f"https://api.example.com/search?q={query}").text How it starts
The opening of the file, as written. The whole thing — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Recovery in LangGraph
Error recovery in LangGraph enables workflows to handle failures gracefully through built-in retry policies, checkpointing for fault tolerance, and custom fallback patterns.
Required Imports
from typing import TypedDict, Optional, Any
from langchain_core.messages import BaseMessage, AIMessage, HumanMessage
from langgraph.graph import StateGraph, START, END
from langgraph.types import RetryPolicy
from langgraph.checkpoint.memory import InMemorySaver
import asyncio
# IMPORTANT: asyncio.timeout requires Python 3.11+
# For Python 3.10: pip install async-timeout && from async_timeout import timeout
RetryPolicy - Built-in Retry Mechanism (Recommended)
LangGraph provides a built-in RetryPolicy for automatic error recovery with exponential backoff and jitter. This is the primary and recommended approach for handling transient failures.
Basic Usage
from typing import TypedDict, Optional, Any
from langgraph.graph import StateGraph, START, END
from langgraph.types import RetryPolicy
class State(TypedDict):
query: str
result: Optional[str]
error: Optional[str]
def api_call_node(state: State) -> dict[str, Any]:
"""Node that calls an external API.
NOTE: Replace `fetch_from_api` with your actual API client.
This is a placeholder function for demonstration.
"""
def fetch_from_api(query: str) -> str:
"""Placeholder for your API client. Replace with actual implementation."""
# Example: return requests.get(f"https://api.example.com/search?q={query}").text
return f"Result for: {query}"
response = fetch_from_api(state["query"])
return {"result": response, "error": None}
# Create workflow with retry policy
workflow = StateGraph(State)
workflow.add_node(
"api_call",
api_call_node,
retry_policy=RetryPolicy(max_attempts=5)
)
workflow.add_edge(START, "api_call")
workflow.add_edge("api_call", END)
graph = workflow.compile()
RetryPolicy Parameters
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.
- 3d ago First seen · 540 lines · 61 tokens per session scan A 0f0d72f50b2e
error-recovery-in-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 4,053 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…