Agent skill · Audited from source
managed-deep-agents
skill · langchain-ai/langchain-skillsMIT licenceAudited 14 Nov 2026 · source 03d2719a5e81
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 03d2719a5e81 and found no filesystem, network or shell access and no hard-coded secrets. What it does: INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can…
Cite
Cite this page
ModelsAtlas. “managed-deep-agents (langchain-ai/langchain-skills)”. Retrieved 14 Nov 2026. https://modelsatlas.com/skills/langchain-ai/managed-deep-agents
Trust audit
Audit 0.4.1 · source read 14 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 03d2719a5e81 · 14 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherlangchain-ai GitHub organizationOwner of the repository this skill is read from
- Source folderlangchain-ai/langchain-skills/config/skills/managed-deep-agentsThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict03d2719a5e81A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can…
---
name: managed-deep-agents
description: "INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can actually do, then scaffolding and deploying it with the mda CLI. Routes to the official docs page for each capability: instructions, skills, tools, MCP, connections, middleware, sandboxes, browser use, memory, identity, subagents, schedules, channels, runtime, Context Hub, deploy, and evals."
---
# Managed Deep Agents
## Overview
Managed Deep Agents (MDA) is a hosted runtime for code-first Deep Agents in LangSmith. You author an agent in Python or TypeScript, test it locally with `mda dev`, and deploy it with `mda deploy`. It runs the open-source Deep Agents harness (see [[deep-agents-core]]) on LangSmith Agent Server, and adds managed sandboxes, browsers, memory, connections, schedules, and channels as project-file declarations.
The core idea is that **an agent is a directory**. A file's location determines its role, and the CLI compiles that directory into a managed LangGraph app.
MDA is in **public beta** on LangSmith Cloud and BYOC data planes.
## The docs are the source of truth
This skill stays thin on purpose. It tells you *what to build and where it goes*; the docs tell you *exactly how*. **Before writing a capability's file, fetch its docs page** from the [feature map](#feature-map) and follow it.
- Fetch the language-specific Markdown page: `https://docs.langchain.com/langsmith/<lang>/managed-deep-agents-<page>.md`, where `<lang>` is `python` or `javascript`. These pages contain only that language's examples.
- Load pages progressively — only the ones the current step needs.
- The full index is at `https://docs.langchain.com/llms.txt`.
- If the docs, this skill, and the installed package disagree, trust `mda --help` and the installed package's types, then the docs, then this skill.
- If you cannot fetch pages (no network), say so, work from this skill and the installed package, and tell the user which pages to check.
## When to use
Use this skill when the user wants to build a Deep Agent in code and run it on LangSmith without operating their own server, or to add a capability to an existing MDA project.
Use a standard LangSmith Deployment instead (see [[langgraph-cli]], `langgraph deploy`) when the user needs custom server routes, a custom LangGraph auth handler, application code around the agent, their own backend/store/checkpointer, or a Python `state_schema`. To convert an existing `create_deep_agent` project, follow the `migrate` page.
# Guide the user through their first agent
When a user is new to MDA, or says anything like "help me build an agent", **do not scaffold immediately**. Run this flow. It costs two questions and prevents building something the platform cannot host.
```text
ask what they want to build -> check it against the limits -> confirm the shape
-> scaffold -> wire the smallest thing that runs -> mda dev -> deploy
```
## 1. Ask what they want to build
Ask in plain language, not in MDA vocabulary. The user does not yet know what a "channel" or a "sandbox" is.
Ask these two things first:
- **What should the agent do?** ("Answer questions about our docs", "triage incoming bugs", "post a summary every morning".)
- **Who or what talks to it, and from where?** (Them in a browser, their app's users, a Slack workspace, a webhook from another system, nobody — it runs on a timer.)
Then ask only the follow-ups that the answers raise:
- Does it need to remember anything between conversations — shared knowledge, or per-person preferences?
- Does it need to reach a private API, or a third-party account on the user's behalf?
- Should anything require a human to approve before it happens?
- Does it need to write files, run code, or use websites that have no API?
Stop asking once you can name the capabilities. Two or three questions is usually enough.
## 2. Check the answer against the limits
Check the request against **[What MDA cannot do](#what-mda-cannot-do)**. If part of it is out of scope, say so in one sentence, offer the nearest supported thing, and keep going with the rest. Do not quietly build a smaller agent and present it as what they asked for.
## 3. Map the answer onto capabilities
Use the [feature map](#feature-map) to turn each need into a file, then read that file's docs page.
## 4. Confirm the shape before writing files
State the plan back in one short block and get agreement. Name the model, and list only the capabilities you are actually going to create:
```text
research-assistant, Python, on openai:gpt-5.5
instructions.md how it researches and cites
tools/search.py web search
schedules/ weekday 8am digest
no memory, no sandbox, no channel
```
## 5. Scaffold and wire the smallest thing that runs
Follow the `quickstart` page. Scaffold with flags that match the plan:
```bash
uvx --from managed-deepagents mda init research-assistant --model openai:gpt-5.5 --no-sandbox
cd research-assistant && uv sync
```
TypeScript: `npx managed-deepagents init research-assistant --model openai:gpt-5.5 --no-sandbox`, then `npm install`. Run `mda` from inside the project (`uv run mda ...` / `npx mda ...`).
Add **one** capability at a time and confirm each works before the next. Do not create files the plan did not call for: a `sandbox/` directory turns on a sandbox (`mda init` scaffolds one unless `--no-sandbox`), and a root `browser.py` turns on a browser.
## 6. Handle keys without touching their secrets
`mda init` writes a `.env` with empty placeholders. Fill in the *names* the project needs and let the user paste the *values*:
- Do not write live credential values into `.env`, copy keys from other projects, or echo key values.
- Confirm `.gitignore` covers `.env` and `.env.*` — `mda init` does this already.
The project needs `LANGSMITH_API_KEY` and its modeExcerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 03d2719
uvx --from managed-deepagents mda init research-assistant --model openai:gpt-5.5 --no-sandbox uv run mda dev # compiles, opens LangSmith Studio uv run mda deploy # syncs Context Hub, uploads, waits for DEPLOYED
git clone https://github.com/langchain-ai/langchain-skills git -C langchain-skills checkout 03d2719a5e81
Commands as the repository documents them: shown, never run by us. Our verdict covers commit 03d2719a5e81 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Claude Code | Mentioned in its text, not tested | Skills for Claude Code · About Claude Code |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
03d2719a5e81
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/langchain-ai/managed-deep-agents/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
mattpocock/skills
Implement a piece of work based on a spec or set of tickets.
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
mattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
Add this badge to your README
[](https://modelsatlas.com/skills/langchain-ai/managed-deep-agents/)
<a href="https://modelsatlas.com/skills/langchain-ai/managed-deep-agents/"><img src="https://modelsatlas.com/skills/langchain-ai/managed-deep-agents/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about managed-deep-agents
Is managed-deep-agents safe to install?
What can managed-deep-agents access on my machine?
Which assistants does managed-deep-agents work with?
How current is this page?
Sources
- github.com/langchain-ai/langchain-skills/tree/main/config/skills — the audited source at commit 03d2719a5e81 and every finding aboveObserved · 14 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- Is managed-deep-agents safe to install?
- What can managed-deep-agents access on my machine?
- Which assistants does managed-deep-agents work with?