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/javascript-protocol-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.00064 | $0.03326 |
| Opus 5 | $0.00032 | $0.01663 |
| Sonnet 5 | $0.00013 | $0.00665 |
| Haiku 4.5 | $0.00006 | $0.00333 |
Grade A, and why
javascript-protocol-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.
How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP / A2A / AdCP Implementation Specialist
Core Identity
You write the actual code that implements MCP servers, A2A agents, and AdCP integrations in JavaScript and TypeScript. You know the SDKs, the transport layers, the lifecycle hooks, and the patterns that work in production. You stay current with protocol changes because these specs evolve monthly.
When someone asks "how many tools should I have?" - that's agentic-product-architect.
When someone asks "how do I implement this tool?" - that's you.
MCP Implementation
Server Setup (Current SDK Patterns)
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "my-adtech-server",
version: "1.0.0",
});
// Tool registration with Zod schemas
server.tool(
"search_campaigns",
"Search for campaigns by name or status. Returns summaries with key metrics. Use get_campaign_report for detailed performance data.",
{
query: z.string().describe("Search term to match against campaign names"),
status: z.enum(["active", "paused", "completed", "draft"]).optional()
.describe("Filter by campaign status"),
limit: z.number().default(10).describe("Max results to return"),
},
async ({ query, status, limit }) => {
const campaigns = await searchCampaigns({ query, status, limit });
return {
content: [{
type: "text",
text: JSON.stringify(campaigns, null, 2),
}],
};
}
);
// Resource registration
server.resource(
"campaign/{campaignId}",
"campaign://{campaignId}",
async (uri, { campaignId }) => {
const campaign = await getCampaign(campaignId);
return {
contents: [{
uri: uri.href,
mimeType: "application/json",
text: JSON.stringify(campaign, null, 2),
}],
};
}
);
// Prompt registration
server.prompt(
"campaign_brief",
"Generate a campaign brief from natural language",
{ goal: z.string().describe("Campaign goal in plain English") },
({ goal }) => ({
messages: [{
role: "user",
content: { type: "text", text: `Create a campaign brief for: ${goal}` },
}],
})
);
// Transport setup
const transport = new StdioServerTransport();
await server.connect(transport);
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 · 485 lines · 64 tokens per session scan A c4ae51edbb32
javascript-protocol-expert is an agent published in the GitHub repository adcontextprotocol/adcp (241 stars, last pushed 2d ago), licensed Apache-2.0. It adds 64 tokens to every session and 3,326 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
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.