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-conformancegit 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-conformance)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/acp-conformance"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-conformance.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.00044 | $0.00887 |
| Opus 5 | $0.00022 | $0.00443 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
acp-conformance 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 7d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Conformance & Production Readiness
Before writing code
Fetch live docs:
- Fetch
https://developers.openai.com/commerce/guides/production/for OpenAI's production readiness checklist - Web-search
site:github.com agentic-commerce-protocol spec openapifor the latest OpenAPI specs to validate against - Web-search
site:github.com agentic-commerce-protocol spec json-schemafor JSON schemas - Fetch
https://developers.openai.com/commerce/guides/get-started/for onboarding requirements
Conformance Test Categories
1. Schema Validation
- Validate all request/response payloads against the ACP JSON schemas
- Ensure monetary amounts are integers in minor currency units (no floats)
- Verify all required fields are present
- Check field types match the spec (string, integer, enum values)
2. Checkout Flow Tests
- Create → verify 201 response with valid CheckoutSession
- Update → verify status transitions are valid
- Retrieve → verify GET returns current state
- Complete → verify payment processing and
completedstatus - Cancel → verify session termination
- Full flow → create → update → complete end-to-end
3. State Machine Compliance
- Verify only valid status transitions occur
- Test
not_ready_for_payment→ready_for_paymentwhen all data provided - Test
authentication_required→completedafter 3DS - Verify
canceledis terminal (no transitions out) - Test concurrent requests on same session
4. Idempotency Tests
- Same
Idempotency-Key+ same body = identical response withIdempotent-Replayed: true - Same key + different body = 422
idempotency_conflict - Concurrent duplicate = 409
idempotency_in_flightwithRetry-After - Keys retained minimum 24 hours
- 5xx responses are NOT cached
5. Header Validation
Authorization: Bearer <token>required on all requestsAPI-Versionrequired and matches spec versionIdempotency-Keyrequired on all POST- Missing required headers → appropriate error response
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.
- 7d ago First seen · 102 lines · 44 tokens per session scan A 5e816411cbd4
acp-conformance 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 887 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-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.
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.
archestra-dev-e2e
Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
fulfill-git-escrow
Fulfill a git escrow bounty by writing a solution or submitting an existing one. Use when the user wants to solve a test suite challenge, write code to pass tests, and claim a token reward. Requires the git-escrows CLI (npm i -g git-escrows).
direct-tests
Write and run fast direct mode tests for GenLayer intelligent contracts.
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.