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-deploymentnpx skills add bdiasti/maestro-bundle-cli --skill deep-agent-deploymentgit 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-deployment)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/deep-agent-deployment"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/deep-agent-deployment.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.00043 | $0.01239 |
| Opus 5 | $0.00022 | $0.00620 |
| Sonnet 5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
deep-agent-deployment 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:8000/api/chat \ How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Agent Deployment
Deploy your Deep Agent as a REST API, WebSocket server, or CLI tool for production use.
When to Use
- When serving the agent as an API endpoint
- When deploying to LangGraph Platform
- When creating a Docker container for the agent
- When building a CLI interface
Available Operations
- Serve as FastAPI REST API
- Add WebSocket streaming
- Deploy with Docker
- Deploy to LangGraph Platform
- Create CLI interface
Multi-Step Workflow
Step 1: FastAPI REST API
# api/server.py
from fastapi import FastAPI, HTTPException
from pydantic import BaseModel
from deepagents import create_deep_agent
from langgraph.checkpoint.postgres import PostgresSaver
app = FastAPI(title="Deep Agent API")
agent = create_deep_agent(
model="anthropic:claude-sonnet-4-6",
checkpointer=PostgresSaver(conn_string=os.environ["DATABASE_URL"])
)
class ChatRequest(BaseModel):
message: str
thread_id: str
class ChatResponse(BaseModel):
response: str
thread_id: str
@app.post("/api/chat", response_model=ChatResponse)
async def chat(req: ChatRequest):
config = {"configurable": {"thread_id": req.thread_id}}
result = agent.invoke(
{"messages": [{"role": "user", "content": req.message}]},
config=config
)
return ChatResponse(
response=result["messages"][-1].content,
thread_id=req.thread_id
)
Step 2: WebSocket Streaming
# api/websocket.py
from fastapi import WebSocket
@app.websocket("/ws/chat/{thread_id}")
async def ws_chat(websocket: WebSocket, thread_id: str):
await websocket.accept()
config = {"configurable": {"thread_id": thread_id}}
while True:
message = await websocket.receive_text()
async for event in agent.astream_events(
{"messages": [{"role": "user", "content": message}]},
config=config,
version="v2"
):
if event["event"] == "on_chat_model_stream":
chunk = event["data"]["chunk"].content
if chunk:
await websocket.send_text(chunk)
await websocket.send_text("[DONE]")
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 · 197 lines · 43 tokens per session scan A c65ae3ab57dd
deep-agent-deployment is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,239 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
toolset-design
Design and validate new MCP toolsets, tools, and tool changes. Use when planning a new toolset, adding tools to an existing toolset, reviewing a toolset PR, or deciding whether a new tool is warranted. Covers the full lifecycle: eval-first validation, tool design methodology, consolidation patterns, and review…
docker-extend
Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
nvca-values-customization
Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.
portainer-mcp-hygiene
How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with select (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret…