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-streaming-executionnpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-streaming-executiongit 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.00079 | $0.03754 |
| Opus 5 | $0.00039 | $0.01877 |
| Sonnet 5 | $0.00016 | $0.00751 |
| Haiku 4.5 | $0.00008 | $0.00375 |
Grade A, and why
streaming-execution-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 — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Streaming Execution in LangGraph
Purpose
Streaming execution enables real-time monitoring of LangGraph workflows by yielding incremental state updates as nodes execute, rather than waiting for complete workflow termination.
When to Use
- Monitor long-running workflows in real-time
- Provide progressive feedback to users
- Debug workflow execution step-by-step
- Build responsive UI applications
- Stream partial results as they're available
- Display LLM tokens as they're generated
Core Pattern
# Instead of app.invoke() which blocks until complete
for event in app.stream(initial_state):
# Process each state update as it occurs
print(event)
Event Structure
Each event is a dictionary mapping node names to their state updates:
for event in app.stream(initial_state):
for node_name, state_update in event.items():
print(f"Node '{node_name}' updated: {state_update}")
Basic Example
from langgraph.graph import StateGraph, START, END
from typing import TypedDict
class State(TypedDict):
messages: list
step: str
def greet_func(state: State) -> dict:
return {"messages": state["messages"] + ["Hello!"], "step": "process"}
def process_func(state: State) -> dict:
return {"messages": state["messages"] + ["Processed."], "step": "done"}
workflow = StateGraph(State)
workflow.add_node("greet", greet_func)
workflow.add_node("process", process_func)
workflow.add_edge(START, "greet")
workflow.add_edge("greet", "process")
workflow.add_edge("process", END)
app = workflow.compile()
# Stream execution
for event in app.stream({"messages": [], "step": ""}):
print(f"Event: {event}")
Output:
Event: {'greet': {'messages': ['Hello!'], 'step': 'process'}}
Event: {'process': {'messages': ['Hello!', 'Processed.'], 'step': 'done'}}
Note: This output format is specific to stream_mode="updates" (the default). Use stream_mode="values" to receive complete state snapshots instead.
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 · 526 lines · 79 tokens per session scan A c30287e2c88d
streaming-execution-in-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 3,754 once invoked, about $0.0004 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.