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-fulfillmentgit 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-fulfillment)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/acp-fulfillment"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-fulfillment/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/acp-fulfillment"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-fulfillment.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.00041 | $0.00675 |
| Opus 5 | $0.00020 | $0.00338 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
acp-fulfillment 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Fulfillment
Before writing code
Fetch live docs:
- Fetch
https://developers.openai.com/commerce/specs/checkout/— fulfillment options are part of the checkout spec - Web-search
site:github.com agentic-commerce-protocol spec json-schema FulfillmentOptionfor the schema - Web-search
site:github.com agentic-commerce-protocol rfcs orders fulfillmentfor fulfillment in orders
Conceptual Architecture
Four Fulfillment Types
| Type | Use Case | Key Fields |
|---|---|---|
| shipping | Physical delivery to address | Carrier, tracking number/URL, delivery windows |
| digital | Downloads, licenses, access | Access URL, license key, expiration date |
| pickup | In-store or locker collection | Location, ready-by window, pickup-by deadline |
| local_delivery | Same-day/local service delivery | Service area, delivery window |
How Fulfillment Works in Checkout
- Create session — Merchant returns available
fulfillment_options[]based on items and address - Agent selects — Agent (or buyer) picks a
fulfillment_option_id - Update session — Agent sends the chosen
fulfillment_option_idin an update - Merchant recalculates — Totals update to include fulfillment cost
- Post-purchase — Merchant emits order updates with tracking and delivery details
FulfillmentOption Object
Each option includes:
id— Unique identifier for this optiontype— One of the four types abovetitle— Display name (e.g., "Standard Shipping")subtitle— Additional info (e.g., "5-7 business days")carrier— Carrier name for shipping- Delivery window (estimated dates/times)
- Pricing — Cost of this fulfillment option
Delivery Windows
Time-based constraints:
- Estimated delivery — Date range for when buyer can expect delivery
- Ready-by (pickup) — When the order will be ready for collection
- Pickup-by (pickup) — Deadline to collect before order is returned
- Delivery window (local delivery) — Time slot for delivery
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 · 72 lines · 41 tokens per session scan A 975489075ce2
acp-fulfillment 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 675 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
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.
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.
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…
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.
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.
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.