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 skills/orcaqubits/agentic-commerce-skills-plugins/ap2-dev-patternsnpx skills add OrcaQubits/agentic-commerce-skills-plugins --skill ap2-dev-patternsgit 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-dev-patterns)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-dev-patterns"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-dev-patterns.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.01416 |
| Opus 5 | $0.00027 | $0.00708 |
| Sonnet 5 | $0.00011 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
ap2-dev-patterns 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 3d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 Development Patterns
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/specification/for the latest protocol details - Fetch
https://ap2-protocol.org/topics/ap2-and-ucp/for UCP integration patterns - Fetch
https://ap2-protocol.org/topics/ap2-and-x402/for x402 crypto integration - Web-search
site:github.com google-agentic-commerce AP2 samplesfor reference architectures
Conceptual Architecture
Multi-Agent Payment Architecture
The standard AP2 architecture involves four agents communicating via A2A:
┌──────────────────────────────────────────────────┐
│ User │
│ (trusted device surface) │
└──────────┬───────────────────────────────────────┘
│ intent + signatures
┌──────────▼───────────────────────────────────────┐
│ Shopping Agent (SA) │
│ Orchestrator — coordinates the full flow │
└──┬──────────────┬────────────────────────────────┘
│ │
│ A2A │ A2A
│ │
┌──▼──────┐ ┌───▼──────────┐
│ Merchant │ │ Credentials │
│ Agent │ │ Provider │
│ │ │ │
│ catalog │ │ payment │
│ cart │ │ methods │
│ signing │ │ tokenization │
└────┬─────┘ └──────────────┘
│
│ (Merchant → MPP)
│
┌────▼─────────────┐
│ Merchant Payment │
│ Processor (MPP) │
│ │
│ authorization │
│ settlement │
│ Payment Mandate │
│ challenges │
└────────┬──────────┘
│
┌────▼──────────┐
│ Network/Issuer │
│ (Visa, MC, │
│ banks) │
└────────────────┘
Important: The SA communicates with the Merchant and the CP via A2A. The Merchant communicates with the MPP. The SA does not directly communicate with the MPP.
UCP Integration Pattern
UCP (Universal Commerce Protocol) operationalizes AP2:
- UCP's Checkout object maps to a commerce-level checkout flow
- UCP's
checkout_mandateis distinct from (but related to) AP2's Cart Mandate —checkout_mandateis a UCP-specific concept that wraps the commerce checkout authorization, while AP2's Cart Mandate is the cryptographically signed VDC binding user consent to specific transaction terms - UCP's
/complete_checkoutAPI = AP2's payment authorization step - PaymentMandate (constructed by the MPP) proves payment authorization for the network/issuer
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.
- 3d ago First seen · 154 lines · 54 tokens per session scan A 7bbff95267e3
ap2-dev-patterns is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (38 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,416 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 skills, from other repositories
chaingpt
Build with the ChainGPT Web3 AI developer platform. Full API/SDK reference and project scaffolding for: Web3 AI Chatbot & LLM, AI NFT Generator, Smart Contract Generator, Smart Contract Auditor, AI Crypto News, AgenticOS Twitter agents, and Solidity LLM. Use when building blockchain apps, Web3 chatbots, NFT tools…
lifi
LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits (Composer), yield discovery (Earn), and intent-based execution (Intents). USE THIS SKILL WHEN USER WANTS TO: Swap tokens between different blockchains (e.g., "swap USDC on Ethereum to ETH on Arbitrum") Bridge tokens to another chain…
near-api-js
Guide for developing with near-api-js v7 - the JavaScript/TypeScript library for NEAR blockchain interaction. Use when: (1) building apps that interact with NEAR blockchain, (2) creating/signing transactions, (3) calling smart contracts, (4) managing accounts and keys, (5) working with NEAR RPC API, (6) handling…
x402-erc7710
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
kleros-curate
Interact with Kleros Curate registries across Ethereum Mainnet, Gnosis Chain, and Sepolia. Use when the user mentions Curate, Light Curate/LightGeneralizedTCR/LGTCR, Stake Curate/PermanentGTCR/PGTCR, Scout, token-curated registry/TCR, token lists, address/CDN tags, Goldsky, MetaEvidence, Verify Your List, or Curate…
magicblock
Design, implement, and debug MagicBlock applications on Solana. Covers Ephemeral Rollups with delegated state; ER/PER architecture and settlement; private payments and token flows; oracles and randomness; scheduling and temporary authority; security and local validation. Use for MagicBlock product selection…