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 acp-orders-webhooksgit 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/acp-orders-webhooks)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/acp-orders-webhooks"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-orders-webhooks.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.1 | $0.00041 | $0.00816 |
| Opus 5 | $0.00020 | $0.00408 |
| Sonnet 5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
acp-orders-webhooks 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Orders & Webhooks
Before writing code
Fetch live docs:
- Web-search
site:github.com agentic-commerce-protocol rfcs ordersfor the orders RFC - Fetch
https://developers.openai.com/commerce/guides/key-concepts/for order lifecycle details - Web-search
site:github.com agentic-commerce-protocol examples ordersfor order webhook examples - Web-search
site:docs.stripe.com agentic-commerce webhookfor Stripe webhook guidance
Conceptual Architecture
Order Lifecycle
After checkout completion, the order moves through these statuses:
created → confirmed → manual_review → processing → shipped → delivered
| | | | | |
+─────────+────────────+──────────────+────────────+──────────+→ canceled
7 statuses:
created— Order placed, payment capturedconfirmed— Merchant acknowledged the ordermanual_review— Requires human review (fraud, compliance)processing— Being prepared for fulfillmentshipped— Handed to carrier (physical) or access granted (digital)delivered— Buyer received the goodscanceled— Order canceled at any stage
Webhook Events
Merchants emit two event types to the agent platform:
order_created— Fired after successful checkout completionorder_updated— Fired on any order status change or update
Webhook Payload
Each webhook event contains:
- Order ID
- Checkout session ID
- Current order status
- Order permalink URL (for buyer to view)
- Fulfillment details (tracking, carrier, delivery windows)
- Line items
- Totals
- Timestamps
HMAC Webhook Signatures
All webhook events MUST be signed:
- Algorithm: HMAC-SHA256
- Header:
Merchant-Signature(or as specified in the latest spec) - Key: Shared secret obtained during onboarding
- Payload: Raw request body (canonical JSON)
- Verification: Timing-safe comparison to prevent timing attacks
Post-Purchase Order Adjustments
ACP supports adjustments after order creation:
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.
- 8d ago First seen · 101 lines · 41 tokens per session scan A bb6f022967ba
acp-orders-webhooks is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 816 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
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.…
archestra-dev-llm-providers
Use when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.
archestra-dev-backend
Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
debridge
Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.
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.
near-intents
Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.