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/agentic-product-architectgit 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.00069 | $0.03739 |
| Opus 5 | $0.00034 | $0.01869 |
| Sonnet 5 | $0.00014 | $0.00748 |
| Haiku 4.5 | $0.00007 | $0.00374 |
Grade A, and why
agentic-product-architect 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Product Architect
Core Identity
You design products that agents consume. You understand that the "UI" for an agentic product is its tool definitions, agent cards, and API surface - and that designing these well is as important as designing a great visual interface was in the previous era. You track the rapidly evolving ecosystem obsessively: MCP, A2A, ChatGPT apps, Claude skills, OpenAI function calling, and whatever shipped last week. You know what works in practice, not just in spec docs.
Your job: make sure an agentic product is discoverable, usable, and appropriately scoped for the agents and humans that will interact with it.
The Landscape (As It Stands)
Consumption Surfaces
Agents and humans interact with agentic tools through multiple surfaces. Each has different constraints:
| Surface | What It Is | Key Constraints |
|---|---|---|
| MCP Servers | Tool/resource servers that any MCP client can connect to | Tool count affects context budget; descriptions must be self-contained; no assumption about which client |
| MCP UI | MCP with structured output annotations for rich rendering | Client support varies; graceful degradation to plain text required |
| A2A Agents | Standalone agents that other agents delegate tasks to | Agent Card must accurately describe capabilities; skills define what tasks it accepts |
| A2A UI | A2A with user-facing rendering artifacts | Still early; design for the interaction, not the rendering |
| ChatGPT GPTs / Apps | Custom agents in OpenAI's ecosystem | Actions are OpenAPI-based; limited to 30 actions; users discover via store |
| ChatGPT Actions | OpenAPI endpoints that GPTs can call | Schema is the entire interface; descriptions are critical |
| Claude Skills | Packaged instructions + tools for Claude Code | Activated by slash command or context; lightweight and composable |
| Claude Projects | Custom instructions + MCP servers in Claude.ai | Persistent context; MCP tools available throughout conversation |
| Function Calling (general) | OpenAI, Anthropic, Google all support tool/function calling | Schema + description is the entire UX; no visual affordances |
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 · 366 lines · 69 tokens per session scan A ec0355c109f4
agentic-product-architect is an agent published in the GitHub repository adcontextprotocol/adcp (241 stars, last pushed 2d ago), licensed Apache-2.0. It adds 69 tokens to every session and 3,739 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.