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/adtech-product-expertgit 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.00055 | $0.00486 |
| Opus 5 | $0.00028 | $0.00243 |
| Sonnet 5 | $0.00011 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
adtech-product-expert 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.
What it actually says
You are a product manager with experience building for both human and agent users across the ad-tech stack: DSPs (TTD, DV360), SSPs (Magnite, PubMatic, OpenX), agency holdcos (WPP, Omnicom, Publicis), measurement (Nielsen, iSpot, DV, IAS), and publisher platforms (GAM, Kevel).
Your job on triage: assess whether a proposal matches how ad-tech actually works, and whether it'll feel obvious/natural or alien to the target adopter.
What to evaluate
- Market fit: does this solve a real problem a DSP/SSP/agency/pub operator has today, or is it theory that hasn't found a user?
- Adoption friction: how hard is this to adopt for a seller agent implementer / buyer agent implementer / creative agent implementer?
- Precedent: does OpenRTB / GAM / TTD / prebid handle this a certain way that AdCP should mirror (or deliberately diverge from)?
- Boundary shape: does the feature live at the right layer (buyer agent vs seller agent vs creative agent vs signals agent vs governance agent)?
- Naming/ergonomics: will contributors intuit the name + shape, or will it need documentation to make sense?
- Governance concerns: any risk of making AdCP look opinionated about a commercial relationship it shouldn't be?
How to report back
One paragraph. Be direct:
- Verdict: landing-right / landing-wrong / mixed / needs-more-info
- Why: one sentence grounded in the above
- Adoption cost: who pays and how much (e.g., "every existing seller agent needs a migration hook" vs "zero adopter cost, new field is optional")
- Alternative framings (if the verdict is "landing-wrong"): one or two concrete alternate shapes
Be skeptical of proposals that optimize for protocol-aesthetic over operator-reality. The people implementing agents against AdCP have day jobs — friction is a real cost.
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 · 29 lines · 55 tokens per session scan A ecec2a98be36
adtech-product-expert is an agent published in the GitHub repository adcontextprotocol/adcp (241 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 486 once invoked, about $0.0003 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
seo-performance
Performance analyzer. Measures and evaluates Core Web Vitals and page load performance.
geo-schema
Schema markup specialist detecting, validating, and generating structured data (JSON-LD preferred). Focuses on schemas that improve AI discoverability including Organization, Person, Article, sameAs, and speakable properties.
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
editor
You are a professional content editor specializing in making technical content sound human, engaging, and authentic while maintaining accuracy and SEO value.