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-vdc-frameworknpx skills add OrcaQubits/agentic-commerce-skills-plugins --skill ap2-vdc-frameworkgit 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-vdc-framework)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-vdc-framework"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-vdc-framework.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.00059 | $0.00931 |
| Opus 5 | $0.00030 | $0.00465 |
| Sonnet 5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
ap2-vdc-framework 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 Verifiable Digital Credentials (VDC) Framework
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/specification/for the VDC framework specification - Fetch
https://ap2-protocol.org/topics/core-concepts/for VDC conceptual overview - Web-search
site:github.com google-agentic-commerce AP2 src/ap2/types mandatefor VDC type definitions - Web-search
ap2 protocol verifiable digital credentials VDCfor community guides
Conceptual Architecture
What VDCs Are
Verifiable Digital Credentials (VDCs) are tamper-evident, portable, and cryptographically signed digital objects that serve as the trust building blocks for AP2 transactions. They provide:
- Non-repudiation — Signed credentials prove who authorized what
- Tamper evidence — Any modification invalidates the signature
- Portability — Credentials can be passed between agents and systems
- Selective disclosure — Only necessary data is revealed to each party
VDC Credential Format
AP2 VDCs use the SD-JWT with Key Binding (+kb) format, enabling selective disclosure and cryptographic holder binding.
JSON payloads are canonicalized using JCS (RFC 8785) before signing to ensure deterministic serialization.
Three VDC Types in AP2
- Cart Mandate — Human-present authorization for a specific cart/transaction
- Intent Mandate — Human-not-present pre-authorization with constraints
- Payment Mandate — Payment ecosystem visibility into agentic transaction context
VDC Lifecycle
1. Creation → Mandate generated (by Merchant for Cart, by SA for Intent)
2. Signing → User signs with hardware-backed device key
3. Presentation → Mandate presented to verifying party
4. Verification → Signature and contents validated
5. Usage → Mandate used to authorize payment
6. Archival → Mandate stored for dispute resolution/audit
Credential Structure
Every VDC follows a common structure:
- Contents — The actual data (transaction details, intent, payment info)
- Signatures — Cryptographic signatures from relevant parties
- Metadata — Timestamps, IDs, version information
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.
- 5d ago First seen · 93 lines · 59 tokens per session scan A 22327c807864
ap2-vdc-framework is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 931 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
metengine-data-agent
Real-time smart money analytics API for Polymarket prediction markets, Hyperliquid perpetual futures, and Meteora Solana LP/AMM pools. 63 endpoints. Pay-per-request via x402 on Solana Mainnet USDC. No API keys.
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…
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…
write-contract
Write production-quality GenLayer intelligent contracts. Always pins concrete GenVM runner version hashes and never uses local-only test/latest runner aliases. Covers equivalence principles, storage rules, LLM resilience, and cross-contract interaction.
intelligent-oracle
Design, deploy, and monitor a GenLayer Intelligent Oracle prediction market from any coding agent. Use when a user wants to create a settled-by-web-evidence prediction market without opening the web UI.
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).