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-dispute-accountabilitygit 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-dispute-accountability)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-dispute-accountability"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-dispute-accountability/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-dispute-accountability"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-dispute-accountability.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.00048 | $0.00996 |
| Opus 5 | $0.00024 | $0.00498 |
| Sonnet 5 | $0.00010 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
ap2-dispute-accountability 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 Dispute Resolution and Accountability
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/specification/for the accountability model - Fetch
https://ap2-protocol.org/topics/core-concepts/for dispute resolution details - Web-search
ap2 protocol dispute accountability liability mandate evidencefor accountability framework - Web-search
ap2 protocol chargeback fraud resolutionfor dispute handling patterns
Conceptual Architecture
Why Accountability Matters
In agentic commerce, the traditional dispute model breaks down:
- Who's responsible when an AI agent buys the wrong item?
- How do you prove the user authorized a purchase?
- What evidence settles a dispute between a user, agent, and merchant?
AP2's VDC-based accountability model provides cryptographic evidence for every dispute scenario.
Liability Allocation Table
| Scenario | Key Evidence | Accountability |
|---|---|---|
| First-party misuse | User-signed Cart/Intent Mandate | User — signature proves authorization |
| Agent mispick (user approved cart) | Cart Mandate shows item, user signed | User — they approved the specific cart |
| Agent mispick (unapproved) | Intent Mandate vs cart discrepancy | Shopping Agent/Platform — exceeded intent |
| Merchant non-fulfillment | Valid mandate + payment confirmation vs absent delivery | Merchant — committed via signature |
| Account takeover | Authentication signals during session | CP/User — depends on auth strength evidence |
| Man-in-the-middle | Digital signature verification | Attack prevented — signatures invalid if tampered |
| Price discrepancy | Merchant-signed Cart Mandate vs charged amount | Merchant — signed specific prices |
| Unauthorized transaction | Absence of user signature on mandate | Platform/Agent — no valid user authorization |
Evidence Chain
For every transaction, AP2 preserves:
- User's original intent — Natural language captured in Intent Mandate
- User's authorization — Cryptographic signature on the mandate
- Merchant's commitment — Merchant entity signature on Cart Mandate
- Payment authorization — Payment Mandate with user signature
- Challenge completion — Records of 3DS/OTP challenges
- Transaction receipt — Payment confirmation from MPP
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.
- 10d ago First seen · 104 lines · 48 tokens per session scan A 8a1ea6d923b3
ap2-dispute-accountability is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 996 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
nla-arbitrate
Manually arbitrate NLA escrow fulfillments as an alternative to the automated oracle. Use when the user wants to review pending arbitration requests, evaluate demands against fulfillments, and submit on-chain decisions. Supports both interactive and LLM-auto modes.
internet-court
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
okx-agent-payments-protocol
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channelid, opening / closing / topping up / settling / refunding a…
jupiter-lend
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
sales-ledger
Provides the Q3 sales ledger workbook for reporting tasks. Use when a task asks you to compute bonuses or totals over the sales ledger; the data lives only in this skill's bundled workbook.
okx-dapp-discovery
Plugin router for 20 third-party DeFi protocols (Polymarket, Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, pump.fun, Uniswap) and their protocol-native tokens (HYPE, HLP, eETH, weETH, stETH, wstETH, LDO, GHO, CAKE, CRV, COMP, RAY, ETHFI…