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 zkp2p/zkp2p-skills --skill peer-checkoutgit clone --depth 1 https://github.com/zkp2p/zkp2p-skillsWrote 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/zkp2p/zkp2p-skills/peer-checkout)<a href="https://agentmods.dev/skills/zkp2p/zkp2p-skills/peer-checkout"><img src="https://agentmods.dev/badge/skills/zkp2p/zkp2p-skills/peer-checkout/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/zkp2p/zkp2p-skills/peer-checkout"><img src="https://agentmods.dev/badge/skills/zkp2p/zkp2p-skills/peer-checkout.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.00023 | $0.00899 |
| Opus 5 | $0.00012 | $0.00449 |
| Sonnet 5 | $0.00005 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
peer-checkout 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 yesterday.
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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Peer Pay checkout orders
Use hosted checkout when a merchant wants customers to pay through supported rails and receive crypto settlement. An order, a payment attempt, and settlement are separate records. Use the merchant API; do not improvise a maker deposit as a merchant checkout.
Set the merchant contract
Resolve merchant environment, server-side API key, authorized recipient and destination chain/token, either exact USDC amount or exact fiat amount/currency, fee payer, permitted rails, and return URLs. Confirm only missing material choices; reuse the merchant's configured defaults when the request intends them. Never put a merchant key in browser code or model-visible logs.
Use @zkp2p/[email protected]. The checked server example creates a USDC-denominated order with exact decimal strings and a bounded request. It writes an order when called. Supply API and checkout origins from the merchant's live environment configuration; do not replace service URLs with peer.xyz based on branding.
- Optionally call
checkQuoteAvailabilitywith the same amount andenabledRails. This is advisory and reserves nothing. If only nearby amounts are available, obtain authorization for an amount change rather than silently resizing the purchase. - Call
createCheckoutserver-side. Use eitherrequestedUsdcAmountorrequestedFiatAmountplusrequestedFiatCurrency, never both. The amount is a human decimal string here, unlike protocol quote base-unit amounts. - Persist the returned order identity and its association with your internal purchase before delivering
checkoutUrl. Treat order tokens/checkout links as sensitive capabilities; do not publish them in issue bodies or analytics. - Send the hosted link through the existing authorized customer flow. A redirect URL, iframe
checkout.successmessage, or customer assertion is a UI signal, not fulfillment authority. - Verify signed server webhooks using the current documented signature scheme and raw-body handling. Read the webhook reference and the merchant environment's current integration docs before implementing verification. Do not invent a header, algorithm, replay window, or shared secret.
- Reconcile events idempotently with the owning order and internal purchase. Release goods/credit on verified
ORDER_FULFILLED. UsePAYMENT_SETTLEDto reconcile actual payout amounts; one settled payment need not fulfill an entire order. A bridged destination can settle a different amount from its quote.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · -321 lines · -36 tokens per session 787814096baa
- 11d ago First seen · 360 lines · 59 tokens per session scan A 65cfe4f8087d
peer-checkout is a skill published in the GitHub repository zkp2p/zkp2p-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 899 once invoked, about $0.0001 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-31.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
agentic-commerce-forthecult
Agentic Commerce skills enables agents to autonomously browse and search for quality lifestyle, wellness, and tech products and gifts, view details, create orders with multi-chain payments (Solana, Ethereum, Base, Polygon, Arbitrum, Bitcoin, Dogecoin, Monero), apply CULT token-holder discounts, and track orders from…
dutch-auction-patterns
Use when implementing Dutch auctions for token sales, NFT mints, fair launch mechanisms, or Gradual Dutch Auctions (GDAs). Covers linear/exponential price decay, batch auctions, and MEV-resistant patterns.
moonpay-commerce
Browse Shopify stores, search products, manage a cart, and checkout with crypto via Solana Pay. No login required.
opensea
Query OpenSea marketplace data — listings, offers, sales / events, floor prices, collection stats, drops, traits — and execute Seaport trades via the official @opensea/cli and OpenSea REST API across Ethereum, Base, Arbitrum, Optimism, Polygon, and more. Includes search across collections / NFTs / tokens / accounts.…