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-checkout-mandategit 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-checkout-mandate)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-checkout-mandate"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-checkout-mandate/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-checkout-mandate"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-checkout-mandate.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.00081 | $0.01211 |
| Opus 5.5 | $0.00032 | $0.00484 |
| Sonnet 5.5 | $0.00016 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
ap2-checkout-mandate 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 Checkout Mandate
Renamed. This credential was called the Cart Mandate in earlier AP2 releases. If you are reading older samples, blog posts, or tutorials that say "Cart Mandate", they are describing this object — but the structure changed along with the name, so do not port field names across. Fetch the live schema.
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/ap2/checkout_mandate/for the current Checkout Mandate schema — open and closed forms. - Fetch
https://ap2-protocol.org/ap2/agent_authorization/for the open/closed mandate model this sits inside. Read that first if you have not; the mandate makes little sense without it. - Fetch
https://ap2-protocol.org/glossary/to catch any further renames. - Web-search
site:github.com google-agentic-commerce AP2 code sdk mandate checkoutfor the current type definitions undercode/.
Conceptual Architecture
What it authorizes
The Checkout Mandate authorizes completing a checkout transaction. It is the credential that says "this user agreed to buy this."
It exists in two forms, matching the open/closed model from the Agent Authorization Framework:
| Form | Bound to a transaction | Used for |
|---|---|---|
| Open | No — carries constraints | Human-not-present: the user authorizes a shape of purchase in advance |
| Closed | Yes — merchant-verified | Human-present, or the resolution of an open mandate |
Open mandate constraints
An open Checkout Mandate bounds what a valid closed mandate may contain:
- Allowed merchants — which merchants may use the mandate
- Line items — acceptable products and quantities
These constraints are the security boundary for autonomous purchasing. The verifier must enforce them; do not rely on the agent to police itself.
Closed mandate shape
The closed form carries the merchant's commitment:
vct— the credential type identifiercheckout_jwt— base64url-encoded, serialized, merchant-signed JWT of the checkout payloadcheckout_hash— cryptographic hash identifying the specific checkoutiat/exp— issued-at and expiry
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.
- 1mo ago First seen · 97 lines · 81 tokens per session scan A c446a8bb0333
ap2-checkout-mandate is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,211 once invoked, about $0.0003 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-09-15.
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.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
archestra-dev-testing
Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
managing-archestra-releases
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.
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.
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…