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 skills add OrcaQubits/agentic-commerce-skills-plugins --skill ap2-shopping-agentgit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-shopping-agent)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-shopping-agent"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-shopping-agent/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/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-shopping-agent"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-shopping-agent.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.00045 | $0.00924 |
| Opus 5 | $0.00023 | $0.00462 |
| Sonnet 5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
ap2-shopping-agent 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 Shopping Agent Implementation
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/specification/for Shopping Agent responsibilities - Web-search
site:github.com google-agentic-commerce AP2 samples roles shopping_agentfor reference implementation - Web-search
site:github.com google-agentic-commerce AP2 samples python src rolesfor source code structure - Fetch SDK docs for agent framework classes (Google ADK)
Conceptual Architecture
What the Shopping Agent Does
The Shopping Agent (SA) is the primary orchestrator of AP2 transactions. It acts as the user's representative, coordinating between all other roles:
- Receives user intent — Understands what the user wants to buy
- Creates Intent Mandates — Formalizes user intent into structured mandates
- Discovers merchants — Finds merchants that can fulfill the intent
- Negotiates with merchants — Presents mandates, receives Cart Mandates
- Coordinates with Credentials Provider — Gets payment methods, handles tokenization
- Manages user interaction — Presents options, collects confirmations
- Orchestrates the full flow — Drives the human-present transaction flow
Note: The Shopping Agent does not create Payment Mandates. Payment Mandates are constructed by the Merchant Payment Processor (MPP).
Agent Card
The Shopping Agent's Agent Card declares:
- AP2 extension support in
capabilities.extensions[] - Skills related to shopping (product search, cart management, payment)
- Authentication requirements for users
- Supported input/output modes
Key Responsibilities
Intent Capture
- Parse user's natural language shopping request
- Extract: what to buy, constraints (price, brand, quality), preferences
- Present structured understanding back to user for confirmation
- Create and present Intent Mandate for signing
Merchant Interaction
- Discover merchant agents (via Agent Cards or registry)
- Present Intent Mandate to relevant merchants
- Receive and evaluate Cart Mandates
- Handle merchant clarification requests
- Support multi-merchant scenarios (compare offers)
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.
- 9d ago First seen · 107 lines · 45 tokens per session scan A 1e1e98faa0e3
ap2-shopping-agent is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 924 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 skills, from other repositories
mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
seller-research
Use when researching a merchant, storefront, marketplace seller, or merchant of record for a buying decision, especially when identity, refund terms, fulfillment, counterfeit risk, domain history, or independent buyer outcomes are uncertain.
design-taste-frontend
Use for visual design direction on greenfield, user-facing surfaces — marketing and landing pages, generated apps, portfolio-style or standalone pages. NOT for routine Archestra platform UI work (dashboards, data tables, settings, forms, existing components) — use archestra-dev-frontend for that. Upstream intent…
lucid-agents
Build, modify, review, debug, or deploy TypeScript services made with the Lucid Agents SDK. Use whenever a project imports @lucid-agents packages or the user asks about Lucid runtimes, entrypoints, adapters, payments, MPP, identity, wallets, A2A tasks, service UI, scaffolding, or deployment.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
migrate-to-archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.