ap2-cart-mandate

ap2-cart-mandate is a skill for Claude Code from OrcaQubits/agentic-commerce-skills-plugins. It costs 56 tokens per session (1,195 once invoked), scanned A, original, MIT.

A guide for implementing the AP2 Cart Mandate, a digitally signed record that ties a person's approval to exact products, prices, and a transaction. In a human-present checkout, the merchant and user both sign it.

In plain words
What is it for?
Use it to build cart creation, merchant signing, user confirmation, signature verification, and other human-present AP2 checkout steps.
Why use it?
It helps ensure that the approved purchase matches the offer and that both the merchant's fulfillment promise and the user's consent can be verified. It requires checking the current AP2 specification for exact fields and types.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ap2-agentic-payments plugin — 18 skills, 1 agent shipped together

Good fit Use it to build cart creation, merchant signing, user confirmation, signature verification, and other human-present AP2 checkout steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-mandate
Install

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.

Any agent
npx skills add OrcaQubits/agentic-commerce-skills-plugins --skill ap2-cart-mandate
Clone the repo
git clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-plugins

Made for: Claude Code.

Or install ap2-agentic-payments, the plugin that ships this one along with the rest of its 18 skills, 1 agent.

Wrote 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.

agentmods badge for ap2-cart-mandate

README.md
[![agentmods](https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-mandate/github.svg)](https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-mandate)
Your own site
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-mandate"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-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.

agentmods 80×15 button for ap2-cart-mandate

Your own site · 80×15
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-mandate"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-cart-mandate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,195 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.01195
Opus 5 $0.00028 $0.00598
Sonnet 5 $0.00011 $0.00239
Haiku 4.5 $0.00006 $0.00120

Measured 10d ago against content hash 041b8216d45a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ap2-cart-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 10d 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.

ap2-agentic-payments/skills/ap2-cart-mandate/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AP2 Cart Mandate

Before writing code

Fetch live docs:

  1. Fetch https://ap2-protocol.org/specification/ for the Cart Mandate schema
  2. Web-search site:github.com google-agentic-commerce AP2 src/ap2/types mandate for the Python type definitions
  3. Web-search site:github.com google-agentic-commerce AP2 samples cart mandate for sample implementations
  4. Fetch https://ap2-protocol.org/topics/core-concepts/ for Cart Mandate conceptual details

Conceptual Architecture

What the Cart Mandate Is

The Cart Mandate is the primary VDC for human-present transactions. It captures explicit user authorization for a specific set of items at specific prices, cryptographically binding the user's identity and consent to the exact transaction details.

Who Creates It

The Merchant Endpoint creates and signs the Cart Mandate after receiving an Intent Mandate from the Shopping Agent. The merchant's signature guarantees fulfillment of the specified items at the specified prices.

Who Signs It

Two signatures are required:

  1. Merchant signature — Entity-level (not agent-level) guarantee of fulfillment
  2. User signature — Hardware-backed device key with in-session authentication

Cart Mandate Structure

A CartMandate has two parts: contents (CartContents) and merchant_authorization (a JWT).

CartContents fields: id, user_cart_confirmation_required, payment_request (W3C PaymentRequest), cart_expiry, merchant_name.

Based on the specification, key fields include:

{
  "contents": {
    "id": "cart_identifier",
    "user_cart_confirmation_required": true,
    "payment_request": {
      "method_data": [
        {
          "supportedMethods": "https://processor.example.com/pay",
          "data": { ... }
        }
      ],
      "details": {
        "id": "order_id",
        "displayItems": [
          { "label": "Product Name", "amount": { "currency": "USD", "value": "29.99" } }
        ],
        "total": {
          "label": "Total",
          "amount": { "currency": "USD", "value": "29.99" }
        },
        "shipping_options": null
      },
      "options": {
        "requestPayerName": true,
        "requestShipping": true,
        "requestPayerEmail": false,
        "requestPayerPhone": false
      }
    },
    "cart_expiry": "2025-09-01T13:00:00Z",
    "merchant_name": "Example Merchant"
  },
  "merchant_authorization": "<base64url-header>..<base64url-signature>"
}

Read the full file on GitHub · 131 lines

Changes

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.

  1. 10d ago First seen · 131 lines · 56 tokens per session scan A 041b8216d45a

Subscribe to this mod's changes

ap2-cart-mandate is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,195 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.

Related

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.

internet-court/internet-court-skill · 45 tokens

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.

cinderline/northcinder · 46 tokens

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…

archestra-ai/archestra · 0 tokens

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.

daydreamsai/lucid-agents · 75 tokens

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.

archestra-ai/archestra · 68 tokens

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-ai/archestra · 73 tokens