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-creationnpx skills add bdiasti/maestro-bundle-cli --skill deep-agent-creationgit 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-creation)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/deep-agent-creation"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/deep-agent-creation.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.00042 | $0.01176 |
| Opus 5 | $0.00021 | $0.00588 |
| Sonnet 5 | $0.00008 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
deep-agent-creation scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( 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 Creation
Create and configure Deep Agents using create_deep_agent() with tools, system prompts, and model selection.
When to Use
- When creating a new Deep Agent from scratch
- When adding custom tools to an agent
- When configuring model and system prompt
- When setting up the main agent entry point
Available Operations
- Install Deep Agents SDK
- Define custom tools
- Create agent with
create_deep_agent() - Run agent with
invoke()orstream() - Configure model provider
Multi-Step Workflow
Step 1: Install
pip install deepagents
# or
uv add deepagents
# For search capability
pip install tavily-python
Step 2: Set API Keys
export ANTHROPIC_API_KEY=your-key
# or
export OPENAI_API_KEY=your-key
Step 3: Define Custom Tools
# agent/tools.py
from langchain.tools import tool
@tool
def search_codebase(query: str, file_pattern: str = "**/*.py") -> str:
"""Search the codebase for files matching a pattern and containing a query."""
import glob
results = []
for filepath in glob.glob(file_pattern, recursive=True):
with open(filepath) as f:
content = f.read()
if query.lower() in content.lower():
results.append(f"Found in {filepath}")
return "\n".join(results) if results else "No matches found"
@tool
def run_tests(test_path: str = "tests/") -> str:
"""Run pytest on the specified path and return results."""
import subprocess
result = subprocess.run(
["pytest", test_path, "-v", "--tb=short"],
capture_output=True, text=True, timeout=120
)
return result.stdout + result.stderr
@tool
def lint_code(path: str = "src/") -> str:
"""Run ruff linter on the specified path."""
import subprocess
result = subprocess.run(
["ruff", "check", path],
capture_output=True, text=True
)
return result.stdout or "No lint issues found"
Step 4: Create the Agent
# agent/main.py
from deepagents import create_deep_agent
from agent.tools import search_codebase, run_tests, lint_code
agent = create_deep_agent(
model="anthropic:claude-sonnet-4-6",
tools=[search_codebase, run_tests, lint_code],
system_prompt="""You are a coding assistant that helps developers write,
test, and review code. You follow clean architecture principles and
always run tests after making changes."""
)
# Run
config = {"configurable": {"thread_id": "session-1"}}
result = agent.invoke(
{"messages": [{"role": "user", "content": "Review the auth module"}]},
config=config
)
print(result["messages"][-1].content)
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 · 42 tokens per session scan A 68e167b97f40
deep-agent-creation is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,176 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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…