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-middlewarenpx skills add bdiasti/maestro-bundle-cli --skill deep-agent-middlewaregit 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-middleware)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/deep-agent-middleware"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/deep-agent-middleware.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.00039 | $0.00918 |
| Opus 5 | $0.00019 | $0.00459 |
| Sonnet 5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
deep-agent-middleware 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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Agent Middleware
Add cross-cutting concerns to Deep Agents with built-in and custom middleware for logging, validation, rate limiting, and tool interception.
When to Use
- When you need to log all tool calls
- When you need to validate inputs before tools execute
- When you need rate limiting on API calls
- When you need custom behavior around tool execution
Available Operations
- Use built-in middleware (TodoList, Filesystem, SubAgent, Summarization)
- Create custom middleware with
@wrap_tool_call - Chain multiple middleware
- Add conditional middleware
Multi-Step Workflow
Step 1: Understand Built-in Middleware
These are automatically active:
| Middleware | What it does | Can disable? |
|---|---|---|
| TodoListMiddleware | write_todos tool for planning |
No |
| FilesystemMiddleware | ls, read_file, write_file, etc. |
No |
| SubAgentMiddleware | task tool for delegation |
No |
| SummarizationMiddleware | Compresses long conversations | No |
| AnthropicPromptCachingMiddleware | Token optimization for Anthropic | Auto |
| PatchToolCallsMiddleware | Repairs broken tool calls | Auto |
Step 2: Create Custom Middleware
# agent/middleware.py
from langchain.agents.middleware import wrap_tool_call
import time
import logging
logger = logging.getLogger(__name__)
@wrap_tool_call
def log_tool_calls(request, handler):
"""Log every tool call with timing."""
start = time.time()
logger.info(f"[TOOL] {request.name} called with: {request.args}")
result = handler(request)
duration = time.time() - start
logger.info(f"[TOOL] {request.name} completed in {duration:.2f}s")
return result
@wrap_tool_call
def validate_file_paths(request, handler):
"""Prevent access to sensitive files."""
if request.name in ("read_file", "write_file", "edit_file"):
path = request.args.get("path", "")
blocked = [".env", "secrets", "credentials", ".git/config"]
if any(b in path for b in blocked):
return f"Access denied: {path} is a protected file"
return handler(request)
@wrap_tool_call
def rate_limit_api_calls(request, handler):
"""Rate limit external API calls."""
api_tools = ["internet_search", "call_api"]
if request.name in api_tools:
time.sleep(1) # Simple rate limit
return handler(request)
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.
- 5d ago First seen · 132 lines · 39 tokens per session scan A 7fa63d84bf4d
deep-agent-middleware is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 918 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…