Agent skill

Langchain Deep Agents

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Build a LangGraph 1.0 Deep Agent — planner + subagents + virtual filesystem + reflection loop — without the state-growth and prompt-inheritance traps.

MITAuto-check passedAI & LLM Engineering

Install Langchain Deep Agents

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langchain-deep-agents -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace langchain-deep-agents --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/langchain-deep-agents .claude/skills/langchain-deep-agents && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
langchain-deep-agents
GitHub stars
2.8k
Token cost
~4.9k tokens
SKILL.md length
1,443 words
Files
6 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Build a LangGraph 1.0 Deep Agent — planner + subagents + virtual filesystem + reflection loop — without the state-growth and prompt-inheritance traps.

  • Works in 7 steps: Understand the four-component architecture → Build the planner prompt skeleton → Construct subagents with EXPLICIT… → …
  • Building a long-horizon agent that must plan
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
  • Calls pip; needs ANTHROPIC_API_KEY and OPENAI_API_KEY

What it does

Langchain Deep Agents is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a LangGraph 1.0 Deep Agent — planner + subagents + virtual filesystem + reflection loop — without the state-growth and prompt-inheritance traps. Use when building a long-horizon agent that must plan, delegate subtasks, work against a scratchpad filesystem, and reflect on progress. Trigger with "langchain deep agent", "planner subagent", "virtual filesystem agent", "reflection loop", "langgraph deep agent".

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/architecture-blueprint.md`, `references/one-pager.md` and `references/reflection-loop.md`). Compatibility notes: Designed for Claude Code

It sits in AI & LLM Engineering, covering Building AI agents and Subagents. It works with LangChain and LangGraph. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Building a long-horizon agent that must plan
  • Delegate subtasks
  • Work against a scratchpad filesystem
  • Reflect on progress

Example prompts

  • “langchain deep agent”
  • “planner subagent”
  • “virtual filesystem agent”
  • “/langchain-deep-agents”

Requirements

  • Python 3
  • A credential in ANTHROPIC_API_KEY
  • A credential in OPENAI_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(python:*)

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Understand the four-component architecture
  2. Build the planner prompt skeleton
  3. Construct subagents with EXPLICIT system-message override
  4. Implement the virtual filesystem with eviction
  5. Add the reflection node with bounded depth
  6. Checkpoint only on user-facing boundaries
  7. Evaluate the full loop with trajectory eval

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(python:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • langchain-ai.github.io
    • blog.langchain.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • ANTHROPIC_API_KEY
    • OPENAI_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Langchain Deep Agents loads about 4.9k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 1,443 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 1,443 words, ~4,859 tokens.

Download SKILL.mdSave it as .claude/skills/langchain-deep-agents/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
langchain-deep-agents
description
Build a LangGraph 1.0 Deep Agent — planner + subagents + virtual filesystem + reflection loop — without the state-growth and prompt-inheritance traps. Use when building a long-horizon agent that must plan, delegate subtasks, work against a scratchpad filesystem, and reflect on progress. Trigger with "langchain deep agent", "planner subagent", "virtual filesystem agent", "reflection loop", "langgraph deep agent".
allowed-tools
Read, Write, Edit, Bash(python:*)
compatibility
Designed for Claude Code
version
2.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, langchain, langgraph, python, langchain-1.0, agents, deep-agents, research

LangChain Deep Agents (Python)

Overview

Two pains bite every team reproducing LangChain's late-2025 Deep Agents blueprint.

Virtual-FS state grows unboundedly (P51). The planner and every subagent write plans, scratch notes, intermediate drafts, and tool outputs into state["files"]. Nothing ever evicts them. After 50 tool calls, the checkpointed state is 8 MB; every MemorySaver.put() takes 400 ms; a run that started at 1.2 s per node visit ends at 2.5 s per node visit. The LangSmith trace viewer times out loading the thread. The user sees latency doubling over the run with no obvious tool-level culprit.

Subagent persona leak (P52). The naive prompt-composition inside the blueprint APPENDS the subagent role message to the parent's system message instead of replacing it. The research-specialist subagent receives: "You are a senior planner coordinating subagents..." + "You are a research specialist..." — and responds as the planner. It produces generic task decomposition instead of the specific lookup you asked for. The bug is invisible in unit tests because both messages "sound right" to a reviewer.

This skill pins to langgraph 1.0.x + langchain-core 1.0.x and walks through the four-component Deep Agent pattern — planner, subagent pool of 3-8 role-specialized workers, virtual filesystem with eviction, reflection node with bounded depth 3-5 — and shows exactly how to avoid P51 (cleanup node + checkpoint-on-boundary) and P52 (explicit SystemMessage(override=True) for every subagent). Pain-catalog anchors: P51, P52.

Prerequisites

  • Python 3.10+
  • langgraph >= 1.0, < 2.0 and langchain-core >= 1.0, < 2.0
  • At least one provider package: pip install langchain-anthropic or langchain-openai
  • Completed skills:
    • langchain-langgraph-agents (L26) — you already know create_react_agent, tool schemas, recursion limits
    • langchain-langgraph-subgraphs (L30) — subagent ≈ subgraph with a bounded contract; if L30 is not yet installed, the subagent construction in Step 3 is self-contained
  • Provider API key: ANTHROPIC_API_KEY or OPENAI_API_KEY
  • Recommended: langchain-eval-harness skill installed for trajectory-level eval

Instructions

Step 1 — Understand the four-component architecture

A Deep Agent has four components. Each has a fixed contract; violating a contract is exactly where P51 / P52 show up.

ComponentInputOutputInvariants
PlannerUser goal, current state["plan"], current state["files"] summary (not full contents)An ordered list of subtasks; each subtask has {subagent_role, instruction, expected_artifact_name}Must NOT write to state["files"] directly. Only emits plan + assignments.
Subagent{subagent_role, instruction, read_files: [names]} from planner{artifact_name, content, status} back to planner via structured outputReceives a fresh SystemMessage with override=True — no parent prompt inheritance (P52). Typical pool size: 3-8.
Virtual FSWrites from subagents (never from planner)Reads by planner (summaries) and subagents (full content)Bounded. Cleanup node evicts entries older than N steps or status=="done" (P51).
ReflectionPlan vs actual artifacts produced, subagent errors, step countDecision: continue / replan / end / escalate_to_humanRuns at most 3-5 times per user-facing turn.

The graph topology:

START -> planner -> (for each subtask) subagent_dispatcher -> virtual_fs_write
                                             |
                                             v
                                        reflection -> planner (replan)
                                                   -> END (done)
                                                   -> interrupt (escalate)

The cleanup node is an edge-less side-effect node hooked onto the reflection transition — it prunes state["files"] before the next planner step runs.

Step 2 — Build the planner prompt skeleton

The planner's prompt must be narrow. It decomposes, assigns, and revises — that is all. It does not answer the user's question itself.

python
PLANNER_SYSTEM = """You are the planner for a Deep Agent.

Your job is to decompose the user's goal into subtasks and assign each to a
specialized subagent. You do NOT execute subtasks yourself.

Available subagent roles: {roles_list}

Return a JSON plan:
{{
  "subtasks": [
    {{"role": "research-specialist",
      "instruction": "Find the most recent SEC 10-K filing for ACME.",
      "expected_artifact": "acme_10k_summary.md",
      "read_files": []}}
  ],
  "reasoning": "Why this decomposition."
}}

Do not write file contents. Do not answer the user directly.
"""

Keep the planner system prompt under ~1500 chars. Long planner prompts leak into subagents if the override=True contract in Step 3 is skipped.

Step 3 — Construct subagents with EXPLICIT system-message override

This is the fix for P52. Never rely on default prompt composition for subagents. Always build a fresh SystemMessage and pass override=True.

python
from langchain_core.messages import SystemMessage, HumanMessage
from langgraph.prebuilt import create_react_agent
from langchain_anthropic import ChatAnthropic

SUBAGENT_PROMPTS = {
    "research-specialist": (
        "You are a research specialist. Given an instruction, produce a "
        "fact-dense summary with inline citations. Return ONLY the summary. "
        "Do NOT plan, do NOT delegate."
    ),
    "code-writer": (
        "You are a code writer. Given a spec, produce runnable Python. "
        "Return ONLY code in one fenced block. Do NOT explain."
    ),
    "critic": (
        "You are a critic. Given an artifact and a spec, list concrete defects. "
        "Return a JSON list of {line, issue, severity}. Do NOT rewrite the artifact."
    ),
}

def build_subagent(role: str, model):
    return create_react_agent(
        model=model,
        tools=ROLE_TOOLS[role],
        # KEY: prompt parameter replaces default state_modifier; override=True
        # means no parent-prompt composition.
        prompt=SystemMessage(content=SUBAGENT_PROMPTS[role]),
    )

def invoke_subagent(subagent, instruction: str, read_files: dict):
    # Build messages from scratch — do not reuse parent message list.
    context = "\n\n".join(f"# {name}\n{content}" for name, content in read_files.items())
    messages = [HumanMessage(content=f"{context}\n\n## Task\n{instruction}")]
    result = subagent.invoke({"messages": messages})
    return result["messages"][-1].content

Rules:

  1. New message list per invocation. Do not pass the planner's message history into the subagent. Build from scratch with HumanMessage(task).
  2. prompt=SystemMessage(...) on create_react_agent replaces the default state_modifier. On LangGraph 1.0.x this is the supported way to pin a subagent's persona.
  3. Return type is a string or a structured JSON artifact — never the full message list. The planner does not need subagent reasoning traces.

See Subagent Prompting for the full override-vs-append test, the handoff structured-output schema, and how to unit-test for P52 persona leak.

Step 4 — Implement the virtual filesystem with eviction

This is the fix for P51. The virtual FS lives in the graph state dict for small artifacts (< 100 KB) and on real disk / an object store for large ones. A cleanup node evicts old entries before every planner step.

python
from typing import TypedDict, Annotated
from operator import or_  # merge dict state updates

class DeepAgentState(TypedDict):
    messages: list
    plan: dict
    files: Annotated[dict, or_]  # {name: {content, written_at_step, status}}
    step: int
    reflection_depth: int

MAX_FILE_AGE_STEPS = 20
INLINE_SIZE_LIMIT_BYTES = 100 * 1024  # 100 KB — above this, spill to disk; keeps state < 500 KB (P51)

def cleanup_node(state: DeepAgentState) -> dict:
    current_step = state["step"]
    kept = {}
    for name, entry in state["files"].items():
        age = current_step - entry["written_at_step"]
        if entry.get("status") == "done" and age > 3:
            continue  # evict completed
        if age > MAX_FILE_AGE_STEPS:
            continue  # evict stale
        kept[name] = entry
    return {"files": kept}

def write_artifact(state, name: str, content: str) -> dict:
    if len(content.encode("utf-8")) > INLINE_SIZE_LIMIT_BYTES:
        # Spill to disk; keep only a pointer in state.
        path = f"/tmp/deep_agent/{state['step']}_{name}"
        with open(path, "w") as f: f.write(content)
        entry = {"content": None, "disk_path": path, "written_at_step": state["step"], "status": "active"}
    else:
        entry = {"content": content, "written_at_step": state["step"], "status": "active"}
    return {"files": {name: entry}}

See Virtual Filesystem Patterns for dict-backed vs disk-backed trade-offs, content-addressed storage for dedup, and a full P51 mitigation procedure with before/after latency numbers.

Step 5 — Add the reflection node with bounded depth

Reflection compares plan vs artifacts produced so far and decides what happens next. Typical reflection depth: 3-5 rounds per user-facing turn. Any higher and the agent is either spinning or should escalate.

python
REFLECTION_SYSTEM = """You are the reflection node of a Deep Agent.

Input: the current plan, the artifacts produced so far (by filename + status),
and the step count. Output a decision:

{"decision": "continue"}           # more subtasks remain, proceed
{"decision": "replan", "reason": "..."}  # current plan is wrong, replanner
{"decision": "end", "final_answer": "..."}  # we are done
{"decision": "escalate", "question": "..."}  # ask the human

Do not rewrite files. Do not invent facts. Base the decision only on what is
present in files and plan.
"""

MAX_REFLECTION_DEPTH = 5

def reflection_node(state: DeepAgentState, model) -> dict:
    if state["reflection_depth"] >= MAX_REFLECTION_DEPTH:
        return {"decision": "escalate", "question": "Max reflection depth reached."}
    # Feed summaries, not full file contents, to the reflection model.
    file_summary = {name: {"status": e["status"], "bytes": len(e.get("content") or "")}
                    for name, e in state["files"].items()}
    msg = HumanMessage(content=f"Plan: {state['plan']}\nFiles: {file_summary}\nStep: {state['step']}")
    result = model.invoke([SystemMessage(content=REFLECTION_SYSTEM), msg])
    return {"decision": result.content, "reflection_depth": state["reflection_depth"] + 1}

See Reflection Loop for the plan-vs-actual diff prompt, self-critique patterns, and the decision tree for replan vs continue vs escalate.

Step 6 — Checkpoint only on user-facing boundaries

Default MemorySaver checkpoints after every node visit. For a Deep Agent that is disastrous: 50 node visits x 160 KB state = 8 MB of serialized state, each write costing 400 ms (P51 root cause).

Fix: checkpoint only at user-facing boundaries — after reflection decides end or escalate, not inside the planner/subagent loop. Use interrupt_after=["reflection"] to get the boundary checkpoint, or switch to a durable store (Postgres / Redis) and override put to no-op during internal steps.

python
from langgraph.checkpoint.memory import MemorySaver
from langgraph.graph import StateGraph, END

checkpointer = MemorySaver()
graph = StateGraph(DeepAgentState)
graph.add_node("planner", planner_node)
graph.add_node("subagent_dispatcher", dispatch_node)
graph.add_node("cleanup", cleanup_node)
graph.add_node("reflection", reflection_node)
graph.set_entry_point("planner")
graph.add_edge("planner", "subagent_dispatcher")
graph.add_edge("subagent_dispatcher", "cleanup")
graph.add_edge("cleanup", "reflection")
graph.add_conditional_edges("reflection", route_after_reflection,
    {"continue": "planner", "replan": "planner", "end": END, "escalate": END})

# Only interrupt on user-facing boundary — the checkpoint taken here is the
# one the user sees and can resume from.
app = graph.compile(checkpointer=checkpointer, interrupt_after=["reflection"])
Show full SKILL.md (601 more words)Show less
Step 7 — Evaluate the full loop with trajectory eval

Unit-testing individual nodes will NOT catch P52 (persona leak is observable only in the subagent's output) or P51 (state growth is observable only over a full run). You need trajectory-level evaluation.

Cross-link: if langchain-eval-harness is installed, use its trajectory-eval pattern with a golden dataset of {goal, expected_final_answer, expected_artifact_set} and assert on: (a) len(pickle.dumps(state)) at turn end < 500 KB, (b) every subagent's first message begins with its role prefix, (c) reflection depth terminated at end or escalate (not hit MAX_REFLECTION_DEPTH silently).

Output

  • Deep Agent graph with four nodes: planner, subagent_dispatcher, cleanup, reflection
  • Subagent pool of 3-8 role-specialized workers, each built with create_react_agent(model, tools, prompt=SystemMessage(...)) — no parent-prompt inheritance (P52 fix)
  • Virtual FS in state["files"] with eviction by age (>20 steps) and status (done + age > 3), disk spill for entries > 100 KB (P51 fix)
  • Reflection node bounded to MAX_REFLECTION_DEPTH=5; escalates to human on cap
  • Checkpointer interrupts only after reflection — user-facing boundary — not every node visit
  • Trajectory-level evaluation hook cross-linked to langchain-eval-harness
State-growth mitigation checklist
  • state["files"] entries carry {written_at_step, status} — not bare content
  • cleanup_node runs before every planner re-entry
  • Entries > 100 KB spill to disk / object store; state holds only a pointer
  • interrupt_after=["reflection"] — checkpoint only on user-facing boundary
  • Reflection feeds summaries {status, bytes} — not raw file contents — to the model
  • len(pickle.dumps(state)) asserted < 500 KB in trajectory tests
  • No state["messages"] accumulation across user turns — reset on boundary

Error Handling

ErrorCauseFix
Subagent response reads like the planner (generic decomposition instead of the specific task)P52 — default prompt composition appended parent system message to subagent's role messagePass prompt=SystemMessage(content=SUBAGENT_PROMPTS[role]) to create_react_agent; build messages from scratch per invocation, do not pass parent history
MemorySaver.put() latency climbs from 20 ms at step 5 to 400 ms at step 50P51 — state["files"] grew to MB-scale and is re-serialized every nodeAdd cleanup_node with age + status eviction; spill > 100 KB entries to disk; switch to interrupt_after=["reflection"] so checkpoint fires only at boundary
LangSmith trace viewer hangs when opening the threadP51 — checkpointed state is megabytes per stepSame fix as above; additionally confirm reflection_node feeds file summaries (bytes + status) not full contents into the model
GraphRecursionError inside the Deep Agent loopPlan never converges; reflection keeps returning continue or replanCap MAX_REFLECTION_DEPTH=5; when hit, force escalate decision so the user gets a checkpoint and a question
Subagent returns full message trace instead of artifactSubagent's prompt did not constrain output formatAdd "Return ONLY the summary" / "Return ONLY code" to the subagent role prompt; validate output shape before writing to state["files"]
KeyError: 'files' during cleanupInitial state shape did not include files: {}Initialize DeepAgentState(messages=[], plan={}, files={}, step=0, reflection_depth=0) at graph entry
Two subagents write the same filename and one overwrites the otherNo dedup / content-addressingNamespace artifact names by {subagent_role}_{step}_{slug}.md, or use content-addressed storage (SHA-256 of content as key)
Agent terminates with end decision but no final answer producedreflection_node decided end before any subagent produced an artifactGuard the end branch with assert any(e["status"] == "done" for e in state["files"].values()) and route to replan otherwise

Examples

Reproducing the Deep Agents reference pattern from scratch

See Architecture Blueprint for the full four-component wiring with copy-paste StateGraph, DeepAgentState, node definitions, and router function — reproducing LangChain's published blueprint with the P51/P52 fixes already applied.

Unit-testing for P52 persona leak
python
def test_subagent_does_not_inherit_planner_persona():
    subagent = build_subagent("research-specialist", model)
    out = invoke_subagent(subagent,
        "What is the capital of France?",
        read_files={})
    # Planner persona says "decompose the goal"; research persona answers directly.
    assert "decompose" not in out.lower()
    assert "subtask" not in out.lower()
    assert "paris" in out.lower()
Asserting state stays bounded over a long run
python
import pickle

def test_state_stays_under_500kb_over_50_steps():
    thread = {"configurable": {"thread_id": "t-bound"}}
    app.invoke({"messages": [HumanMessage("Run a 50-step synthesis task")]}, config=thread)
    final = app.get_state(thread).values
    assert len(pickle.dumps(final)) < 500_000, "P51 regression: state > 500 KB"

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/.curated/langchain-deep-agents of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/architecture-blueprint.md
  • references/one-pager.md
  • references/reflection-loop.md
  • references/subagent-prompting.md
  • references/virtual-filesystem-patterns.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Langchain Deep Agents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Langchain Deep Agents compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Langchain Deep Agents this skilljeremylongshore/tons-of-skills-marketplace2.8k—~4.9kAutomated safety check: PassMIT
Deep Agents Corelangchain-ai/langchain-skills1.3k—~3.1kAutomated safety check: PassMIT
Deep Agentslangchain-ai/docs426—~1.1kAutomated safety check: PassMIT
Mem0 Platform SDKmem0ai/mem067k1 repos~2.2kAutomated safety check: PassApache-2.0
LangSmith Trace DebuggingComposioHQ/awesome-claude-skills77k8 repos~2.7kAutomated safety check: PassNone
Add Example AgentGetBindu/Bindu10k—~1.1kAutomated safety check: NotesCustom licence

Similar skills

  • Deep Agents Core

    langchain-ai/langchain-skills

    Official

    Explains how to build agents with the Deep Agents framework: create_deep_agent, the built-in middleware, the harness, SKILL.md format and configuration options.

    1.3k GitHub stars~3.1k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • Deep Agents

    langchain-ai/docs

    Official

    Build batteries-included agents with planning, context management, subagent delegation, and sandboxed execution.

    426 GitHub stars~1.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.

    67k GitHub starsUsed in 1 repo~2.2k tokens
    AI & LLM EngineeringAuto-check passed
  • LangSmith Trace Debugging

    ComposioHQ/awesome-claude-skills

    Debugs LangChain and LangGraph agents by pulling recent execution traces with the langsmith-fetch CLI and reporting errors, tool calls, timings and token use.

    77k GitHub starsUsed in 8 repos~2.7k tokens
    AI & LLM EngineeringAuto-check passed
  • Add Example Agent

    GetBindu/Bindu

    Add a new self-contained example agent under examples/. An agent skill from GetBindu/Bindu.

    10k GitHub stars~1.1k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Failproof AI SDK Integration

    FailproofAI/failproofai

    Helps instrument a custom Python or TypeScript agent to record events for Failproof AI, verify what gets written, and run an evaluator worker that scores the runs.

    5.3k GitHub stars~6k tokensUpdated 4 days ago
    AI & LLM EngineeringAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Langchain Deep Agents

What does Langchain Deep Agents do?

Build a LangGraph 1.0 Deep Agent — planner + subagents + virtual filesystem + reflection loop — without the state-growth and prompt-inheritance traps. Langchain Deep Agents is an agent skill from jeremylongshore/tons-of-skills-marketplace.0 Deep Agent — planner + subagents + virtual filesystem + reflection loop — without the state-growth and prompt-inheritance traps.

When should I use Langchain Deep Agents?

Langchain Deep Agents fits situations like: building a long-horizon agent that must plan; delegate subtasks; work against a scratchpad filesystem; reflect on progress.

How do I install Langchain Deep Agents in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langchain-deep-agents -a claude-code`. Or copy the skill folder (skills/.curated/langchain-deep-agents in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/langchain-deep-agents in your project. Claude Code loads it when a task matches its description.

How do I install Langchain Deep Agents in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langchain-deep-agents -a codex`. Or copy the skill folder (skills/.curated/langchain-deep-agents in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/langchain-deep-agents in your project. Codex loads it when a task matches its description.

Can I use Langchain Deep Agents in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langchain-deep-agents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/langchain-deep-agents, .gemini/skills/langchain-deep-agents, .github/skills/langchain-deep-agents and .opencode/skills/langchain-deep-agents in your project.

What does Langchain Deep Agents need to run?

Going by SKILL.md and its folder, Langchain Deep Agents needs the command-line tools its instructions call (pip) and credentials named ANTHROPIC_API_KEY and OPENAI_API_KEY. Our summary lists: Python 3; A credential in ANTHROPIC_API_KEY; A credential in OPENAI_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(python:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Langchain Deep Agents access the network?

SKILL.md names 2 domains. As links in the text: langchain-ai.github.io and blog.langchain.com. This is read from the text; nothing was executed.

Is Langchain Deep Agents safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Langchain Deep Agents use?

Langchain Deep Agents is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Langchain Deep Agents use?

About 4.9k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.2k tokens, read only when the agent opens those files.

What are the alternatives to Langchain Deep Agents?

Skills that share tags, products or a category with Langchain Deep Agents: Deep Agents Core (langchain-ai/langchain-skills, 1.3k stars), Deep Agents (langchain-ai/docs, 426 stars), Mem0 Platform SDK (mem0ai/mem0, 67k stars) and LangSmith Trace Debugging (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Langchain Deep Agents?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.