Deep Agents is an extensible agent harness that provides an out-of-the-box agent for long, multi-step tasks, with features such as planning, sub-agents, filesystem access, context management, memory, and human approval of tool calls. It is used by developers building agents with different language models, and its catalogue entries extend the harness with reusable skills, MCP servers, and instructions.
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 langchain-ai/deepagents --skill data-visualizationgit clone --depth 1 https://github.com/langchain-ai/deepagentsWrote 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/langchain-ai/deepagents/data-visualization)<a href="https://agentmods.dev/skills/langchain-ai/deepagents/data-visualization"><img src="https://agentmods.dev/badge/skills/langchain-ai/deepagents/data-visualization/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/langchain-ai/deepagents/data-visualization"><img src="https://agentmods.dev/badge/skills/langchain-ai/deepagents/data-visualization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 337 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00040 | $0.03149 |
| Opus 5.5 | $0.00016 | $0.01260 |
| Sonnet 5.5 | $0.00008 | $0.00630 |
| Haiku 4.5 | $0.00004 | $0.00315 |
Grade A, and why
data-visualization 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Visualization Skill
Create publication-quality analytical charts using matplotlib and seaborn in a headless GPU sandbox. Charts are saved as PNG files to /workspace/ for retrieval.
When to Use This Skill
Use this skill when:
- Visualizing results from cuDF analysis or cuML models
- Creating charts (bar, line, scatter, heatmap, histogram, box plot)
- Building multi-panel analysis summaries
- The user asks for visual output, plots, graphs, or charts
- Presenting statistical findings with figures
Initialization (REQUIRED)
MUST call matplotlib.use('Agg') BEFORE importing pyplot. This enables headless rendering.
import matplotlib
matplotlib.use('Agg') # Headless backend — MUST be before pyplot import
import matplotlib.pyplot as plt
import numpy as np
# Publication-quality defaults
plt.rcParams.update({
'figure.dpi': 100,
'savefig.dpi': 300,
'font.size': 11,
'axes.labelsize': 12,
'axes.titlesize': 14,
'xtick.labelsize': 10,
'ytick.labelsize': 10,
'legend.fontsize': 10,
'figure.constrained_layout.use': True,
})
# Colorblind-safe palette (Okabe-Ito)
COLORS = ['#0173B2', '#DE8F05', '#029E73', '#D55E00', '#CC78BC',
'#CA9161', '#FBAFE4', '#949494', '#ECE133', '#56B4E9']
Saving Charts
Always save to /workspace/ with these settings:
plt.savefig('/workspace/chart_name.png', dpi=300, bbox_inches='tight',
facecolor='white', edgecolor='none')
plt.close()
# IMPORTANT: call read_file("/workspace/<chart>.png") to display inline
dpi=300for print qualitybbox_inches='tight'removes excess whitespacefacecolor='white'ensures white background- Always call
plt.close()after saving to free memory
Displaying Charts (REQUIRED)
After saving any chart, you MUST call read_file on it to display it inline in the conversation:
read_file("/workspace/chart_name.png")
Users cannot see charts unless you do this. Every chart you save MUST be followed by a read_file call.
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 First seen · 344 lines · 40 tokens per session scan A fbae91eefde1
data-visualization is a skill published in the GitHub repository langchain-ai/deepagents (30,344 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 3,149 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-08-30.
Other skills, from other repositories
recover-from-failure
How to recover when a tool call fails — diagnose, not blindly retry.
workspace-conventions
Reminders about how Dawn's workspace tools behave and what the path-jail allows.
dawn
Build AI agents and workflows with the Dawn framework — the TypeScript meta-framework for LangGraph. Use when creating, editing, or debugging a Dawn app (routes, tools, state, agents, workflows, testing, deployment).
cite-sources
How to attribute every factual claim to a corpus document.
synthesize-findings
How to merge researcher sub-answers into one cited report.
code-reviewer
A code-review guide written in Chinese for examining source code for bugs, security risks, performance problems, and quality issues.