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/acp-setupnpx skills add OrcaQubits/agentic-commerce-skills-plugins --skill acp-setupgit 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-setup)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/acp-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-setup.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.00044 | $0.00734 |
| Opus 5 | $0.00022 | $0.00367 |
| Sonnet 5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
acp-setup 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Project Setup
Before writing code
- Fetch the latest spec version: Web-search
site:github.com agentic-commerce-protocol CHANGELOGfor the current spec version - Fetch the OpenAPI specs: Fetch from
https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/tree/main/spec— download the latest versioned checkout and delegate-payment OpenAPI YAML files - Fetch the get-started guide: Fetch
https://developers.openai.com/commerce/guides/get-started/for onboarding steps - Check for SDK packages: Search PyPI for
agentic-commerce-protocoland npm for ACP-related packages. Note: there is no official standalone SDK — most implementations use the OpenAPI spec directly or reference implementations like Medusa.js
What This Skill Does
Scaffolds a new ACP merchant server project:
- Detect language/framework — Python (FastAPI/Flask/Django), TypeScript (Express/Fastify/Medusa), Go, etc.
- Install dependencies — HTTP framework, JSON schema validation, HMAC library, UUID generation
- Import OpenAPI spec — Download the latest versioned spec from the GitHub repo
- Create configuration — Environment variables for API keys, webhook secrets, API version, PSP credentials
- Stub endpoints — Create route stubs for the 5 checkout operations + webhook receiver
- Set up middleware — Bearer token auth, idempotency key extraction, API version header validation, request logging
Configuration Essentials
These must be externalized (env vars or config file):
ACP_API_KEY— Bearer token for authenticationACP_API_VERSION— Spec version (YYYY-MM-DD format)ACP_WEBHOOK_SECRET— HMAC signing key for webhooksSTRIPE_API_KEY— If using Stripe as PSP for delegated paymentACP_MERCHANT_ID— Merchant identifier for SPT scoping
Project Structure Pattern
merchant-server/
├── config/ # Environment and settings
├── routes/
│ ├── checkout.py/ts # 5 checkout endpoints
│ ├── webhooks.py/ts # Webhook receiver
│ └── health.py/ts # Health check
├── middleware/
│ ├── auth.py/ts # Bearer token validation
│ ├── idempotency.py/ts # Idempotency key handling
│ └── versioning.py/ts # API-Version header validation
├── models/ # Data models from JSON schema
├── services/
│ ├── checkout.py/ts # Business logic
│ ├── payment.py/ts # PSP integration
│ └── inventory.py/ts # Stock management
├── schemas/ # OpenAPI + JSON schemas
└── tests/
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 · 60 lines · 44 tokens per session scan A 60b94abc724c
acp-setup is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 734 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.
store-listing-localizer
Automate Microsoft Store (Partner Center) listing localization for Intelligent Terminal (Store ID 9NMQC2SSJX24). Use when asked to export/import Store listings, localize release notes / descriptions / captions / features into 80+ languages, update listingData CSV, or push Store listing translations without manually…
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.