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-human-in-the-loopnpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-human-in-the-loopgit 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-human-in-the-loop)<a href="https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/langgraph-dev-human-in-the-loop"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/langgraph-dev-human-in-the-loop.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.00097 | $0.01864 |
| Opus 5 | $0.00048 | $0.00932 |
| Sonnet 5 | $0.00019 | $0.00373 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
langgraph-dev-human-in-the-loop 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 4d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human-in-the-Loop with LangGraph
Enable human intervention at any point in your LangGraph workflow for approval gates, content review, input validation, and feedback loops. Human-in-the-loop is a core LangGraph differentiator that allows indefinite pauses with persistent state, making it ideal for production agents requiring human oversight.
When to Use This Pattern
- Approval gates: Pause before critical actions (API calls, database writes, financial transactions)
- Content review: Allow humans to review and edit LLM-generated content before proceeding
- Tool approval: Review tool calls before execution
- Input validation: Validate user input in multi-turn conversations
- Feedback loops: Incorporate human feedback to guide agent behavior
Core Concepts
Dynamic Interrupts with interrupt()
Dynamic interrupts (recommended for production) pause graph execution from within a node based on the current state. Use the interrupt() function to request human input, which gets surfaced to the client. The graph remains paused until resumed with a value via the Command primitive.
from langgraph.types import interrupt, Command
from langgraph.checkpoint.memory import InMemorySaver
def approval_node(state: State):
# Pause and request approval
approved = interrupt({
"question": "Do you approve this action?",
"details": state["action_details"]
})
return {"approved": approved}
# Compile with checkpointer (required for interrupts)
memory = InMemorySaver()
graph = workflow.compile(checkpointer=memory)
# Initial run - hits interrupt
config = {"configurable": {"thread_id": "thread-1"}}
result = graph.invoke({"action_details": "..."}, config=config)
# Resume with human decision
graph.invoke(Command(resume=True), config=config)
Requirements:
- ✅ Must enable a checkpointer (e.g.,
InMemorySaver,SqliteSaver) - ✅ Must provide a thread_id in config
- ✅ Resume with
Command(resume=<value>)
What ships with it
11 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.
- examples/approval-workflow.py 4.3 KB runs code
- examples/review-and-edit.py 5.1 KB runs code
- examples/tool-approval.py 8.1 KB runs code
- examples/validation-loop.py 6.1 KB runs code
- references/advanced-workflows.md 15 KB
- references/interrupt-patterns.md 14 KB
- references/static-interrupts.md 12 KB
- test-env/.python-version 5 B
- test-env/main.py 86 B runs code
- test-env/pyproject.toml 187 B
- test-env/uv.lock 136 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.
- 4d ago First seen · 220 lines · 97 tokens per session scan A 172b7b73baf1
langgraph-dev-human-in-the-loop is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,864 once invoked, about $0.0005 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.
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…