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 skills add jnPiyush/AgentX --skill langgraphgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/langgraph)<a href="https://agentmods.dev/skills/jnpiyush/agentx/langgraph"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/langgraph/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jnpiyush/agentx/langgraph"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/langgraph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00046 | $0.01249 |
| Opus 5.5 | $0.00018 | $0.00500 |
| Sonnet 5.5 | $0.00009 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LangGraph
WHEN: Building stateful agent orchestration with explicit graph nodes, durable execution, checkpointing, interrupts, subgraphs, or LangSmith-observed agent workflows.
When to Use
- Building multi-step agents with explicit state transitions
- Implementing durable, resumable workflows for long-running tasks
- Adding human approval or interruption points into agent execution
- Modeling branching, loops, retries, and subgraphs explicitly
- Using LangSmith to inspect trajectories, state changes, and failures
Decision Tree
Need agent orchestration?
+- Mostly linear workflow with simple tool calls?
| +- Use plain agent framework first
| - Add LangGraph only if state and branching become explicit requirements
+- Need durable state across steps or resumes?
| - Use LangGraph StateGraph with checkpointing
+- Need human approval or editing of state mid-run?
| - Use interrupts / human-in-the-loop nodes
+- Need reusable workflow segments?
| - Use subgraphs with narrow state contracts
+- Need production debugging visibility?
| - Add LangSmith tracing and run metadata
-- Need complex branching and retries?
- Model them as graph edges, not implicit prompt instructions
Core Rules
- Model workflow state explicitly with typed schemas rather than ad hoc dictionaries everywhere.
- Keep node responsibilities narrow: one decision, one transformation, or one external action.
- Put retries, branching, and approval steps in the graph, not only inside prompts.
- Persist checkpoints for any workflow that may exceed one request/response turn or need recovery.
- Trace graph execution so failures can be tied to node transitions and state mutations.
Architecture Pattern
User Input
-> StateGraph entry
-> planner node
-> tool/research node(s)
-> validation node
-> human approval interrupt (optional)
-> writer/executor node
-> final response node
Minimal Pattern
from typing_extensions import TypedDict
from langgraph.graph import START, END, StateGraph
class AgentState(TypedDict):
question: str
answer: str
def draft_answer(state: AgentState) -> dict:
return {"answer": f"Draft response for: {state['question']}"}
graph = StateGraph(AgentState)
graph.add_node("draft_answer", draft_answer)
graph.add_edge(START, "draft_answer")
graph.add_edge("draft_answer", END)
app = graph.compile()
result = app.invoke({"question": "What should we build?", "answer": ""})
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.
- 1mo ago Changed 68e9aa132223
- 1mo ago First seen · 146 lines · 46 tokens per session scan A 332694211436
langgraph is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,249 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…