Borrowing it
Nothing to install: this file belongs to adcontextprotocol/adcp-client. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adcontextprotocol/adcp-client/main/AGENTS.mdgit clone --depth 1 https://github.com/adcontextprotocol/adcp-clientWrote 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/instructions/adcontextprotocol/adcp-client/agents-md)<a href="https://agentmods.dev/instructions/adcontextprotocol/adcp-client/agents-md"><img src="https://agentmods.dev/badge/instructions/adcontextprotocol/adcp-client/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/adcontextprotocol/adcp-client/agents-md"><img src="https://agentmods.dev/badge/instructions/adcontextprotocol/adcp-client/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.03653 | $0.03653 |
| Opus 5.5 | $0.01461 | $0.01461 |
| Sonnet 5.5 | $0.00731 | $0.00731 |
| Haiku 4.5 | $0.00365 | $0.00365 |
Grade A, and why
adcp-client AGENTS.md 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 yesterday.
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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Assistant Instructions for AdCP Client
This document contains essential guidelines for AI coding assistants (Claude, Copilot, etc.) working on the AdCP Client project.
Start Here
Protocol overview — Read docs/llms.txt for a single-file summary of AdCP: all 72 tools, key types, error codes, common flows, and test scenarios. Also available at https://adcontextprotocol.github.io/adcp-client/llms.txt
Type reference — Read docs/TYPE-SUMMARY.md for curated type signatures (AgentConfig, TaskResult, ConversationContext, and all tool request/response shapes).
Do NOT read these files — they are large generated files that waste context:
src/lib/types/tools.generated.ts(~13,000 lines) — use TYPE-SUMMARY.md insteadsrc/lib/types/core.generated.ts(~2,000 lines) — use TYPE-SUMMARY.md insteadsrc/lib/types/schemas.generated.ts(~8,000 lines) — Zod runtime schemas, rarely needed directlysrc/lib/agents/index.generated.ts— generated Agent classes, use the client API instead
Building a server-side agent? — Read docs/guides/BUILD-AN-AGENT.md and the published compliance storyboards at https://adcontextprotocol.org/compliance/{version}/ (mirrored locally in compliance/cache/{version}/ after npm run sync-schemas).
Testing an agent for conformance? — Read docs/guides/CONFORMANCE.md and call runConformance(agentUrl, opts) from @adcp/sdk/conformance. Property-based fuzzing against the bundled JSON schemas; stateless tier covers 11 discovery tools across every protocol.
Migration guides — AdCP 2 retirement (AdCP 3-only discovery, removed compatibility APIs, and last supporting SDK pins); Account change feed (wake-up parsing, guarded bootstrap/drain, subscriber registration and ownership boundaries); docs/migration-6.6-to-6.7.md (fifteen adopter recipes; two breaking changes — 'implicit' enforces inline-account_id refusal and SalesPlatform split into SalesCorePlatform & SalesIngestionPlatform; plus definePlatform helpers, composeMethod, accounts.resolve security presets, accounts.upsert/list/syncGovernance(ctx), typed errors, issues[].hint, BuyerAgentRegistry, createTenantRegistry, createOAuthPassthroughResolver, createRosterAccountStore, createTenantStore w/ built-in tenant gate, MEDIA_BUY_TRANSITIONS lifecycle helpers, createMediaBuyStore for targeting_overlay echo, NoAccountCtx narrow, refAccountId(ref)); docs/migration-5.x-to-6.x.md (5 → 6 framework shape); docs/migration-4.x-to-5.x.md (4 → 5); docs/migration-buyer-agent-registry.md (registry deep-dive).
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.
- yesterday Changed · +3 tokens per session 3b4c5ee2866d
- 5d ago Changed · +2 lines · +95 tokens per session f4e0a17ac3e2
- 6d ago Changed · +45 tokens per session a0b396bf938e
- 9d ago Changed 1ce28687e382
- 14d ago First seen · 339 lines · 3,510 tokens per session scan A d338472dd4d9
adcp-client AGENTS.md is an instructions file published in the GitHub repository adcontextprotocol/adcp-client (18 stars, last pushed today), licensed Apache-2.0. It adds 3,653 tokens to every session, about $0.0146 per session on Opus 5.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-10-13.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.