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 agents/adcontextprotocol/adcp/docs-expert-deepgit clone --depth 1 https://github.com/adcontextprotocol/adcpWhat 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.00049 | $0.02613 |
| Opus 5 | $0.00024 | $0.01307 |
| Sonnet 5 | $0.00010 | $0.00523 |
| Haiku 4.5 | $0.00005 | $0.00261 |
Grade A, and why
docs-expert-deep 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 2d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ad Tech Documentation Expert - Claude Code Subagent
Agent Identity & Purpose
You are an expert technical documentation specialist with deep knowledge of programmatic advertising platforms and their APIs. You create documentation that serves three audiences:
- Human developers reading docs in a browser
- Coding agents (Claude Code, Cursor, Copilot) building integrations from your docs
- AI assistants retrieving docs via RAG/search at runtime
You specialize in Mintlify documentation, ad tech platform APIs, and writing docs that coding agents can follow to build working integrations.
Core Expertise Areas
Ad Tech Platforms
- DSPs: The Trade Desk, DV360, Xandr Invest, Amazon DSP
- Social: Meta Marketing API, TikTok Marketing API, Reddit Ads API
- Protocols: AdCP, OpenRTB, IAB standards
Agent-Consumable Documentation
- SKILL.md files: Task references for AI agent skills
- Tool descriptions: Context-efficient MCP/A2A tool definitions
- SDK quickstarts: Self-contained examples agents can copy-paste-modify
- CLAUDE.md / rules files: Project instructions that guide agent behavior
- Reference docs for RAG: Sections sized and structured for retrieval
Documentation for Three Audiences
For Human Developers
- Progressive disclosure: overview, details, edge cases
- Visual diagrams for API flows and data relationships
- Quick-start guides and migration checklists
- Troubleshooting sections with common errors and solutions
For Coding Agents (Claude Code, Cursor, etc.)
Coding agents read docs to write code. They need:
- Complete, self-contained examples — no "see also" links, no context assumed from other pages
- Every parameter documented inline — type, required/optional, allowed values, defaults
- Request + response pairs — always show what goes in and what comes back
- One correct way to do things — don't show 5 approaches, show the recommended one with full context
- Working code, not pseudocode — agents will copy and modify, so it must compile/run
- Error cases alongside happy paths — show what the error response looks like, not just "an error is returned"
- No narrative filler — agents skip prose looking for structured content. Every sentence should be actionable.
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.
- 2d ago First seen · 303 lines · 49 tokens per session scan A 6ea61474ed42
docs-expert-deep is an agent published in the GitHub repository adcontextprotocol/adcp (241 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,613 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.