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/bdiasti/maestro-bundle-cli/deep-agent-backendsnpx skills add bdiasti/maestro-bundle-cli --skill deep-agent-backendsgit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWrote 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/bdiasti/maestro-bundle-cli/deep-agent-backends)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/deep-agent-backends"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/deep-agent-backends.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.00046 | $0.01236 |
| Opus 5 | $0.00023 | $0.00618 |
| Sonnet 5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
deep-agent-backends 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Agent Backends
Configure how your Deep Agent stores files and manages context. Backends determine where files live — in memory, on disk, in a database, or in a sandbox.
When to Use
- When choosing between ephemeral vs persistent storage
- When the agent needs local filesystem access
- When you need shell execution capability
- When routing different paths to different storage
- When running in sandboxed environments (Modal, Daytona)
Available Operations
- Use StateBackend (ephemeral, default)
- Use FilesystemBackend (local disk)
- Use StoreBackend (persistent, cross-thread)
- Use LocalShellBackend (filesystem + shell)
- Use CompositeBackend (route paths to backends)
- Use Sandboxes (isolated execution)
Multi-Step Workflow
Step 1: Choose Your Backend
| Backend | Persistence | Shell | Use when |
|---|---|---|---|
| StateBackend | Ephemeral (1 thread) | No | Prototyping, stateless tasks |
| FilesystemBackend | Local disk | No | Read/write project files |
| StoreBackend | DB (cross-thread) | No | Persistent memory, multi-session |
| LocalShellBackend | Local disk | Yes | Full coding agent (like Claude Code) |
| CompositeBackend | Mixed | Mixed | Different storage per path |
| Sandboxes | Isolated | Yes | Untrusted code execution |
Step 2: StateBackend (Default)
from deepagents import create_deep_agent
# Uses StateBackend automatically — files live in memory, gone after session
agent = create_deep_agent(model="anthropic:claude-sonnet-4-6")
Step 3: FilesystemBackend (Local Files)
from deepagents import create_deep_agent
from deepagents.backends import FilesystemBackend
agent = create_deep_agent(
model="anthropic:claude-sonnet-4-6",
backend=FilesystemBackend(root_dir=".", virtual_mode=True)
)
# Agent can now read/write files in the project directory
Step 4: LocalShellBackend (Full Coding Agent)
from deepagents import create_deep_agent
from deepagents.backends import LocalShellBackend
# WARNING: Agent can execute shell commands on your machine
agent = create_deep_agent(
model="anthropic:claude-sonnet-4-6",
backend=LocalShellBackend(
root_dir=".",
env={"PATH": "/usr/bin:/bin", "HOME": "/home/user"}
)
)
# Agent can now: read/write files, run shell commands, install packages
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 · 166 lines · 46 tokens per session scan A 612c856683c0
deep-agent-backends is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 1,236 once invoked, about $0.0002 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-30.
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…