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-delegate-authenticationgit 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-delegate-authentication)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/acp-delegate-authentication"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-delegate-authentication/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-delegate-authentication"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-delegate-authentication.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.00065 | $0.01104 |
| Opus 5.5 | $0.00026 | $0.00442 |
| Sonnet 5.5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
acp-delegate-authentication 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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Delegate Authentication (3DS)
Before writing code
Fetch live spec — this API arrived in the 2026-04-17 release:
- Fetch
https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/releasesfor the current spec version. - Fetch
spec/<version>/openapi/openapi.delegate_authentication.yaml— authoritative for paths, request fields, statuses, and headers. - Fetch
spec/<version>/json-schema/schema.delegate_authentication.jsonfor the schemas. - Read
acp-delegated-paymentalongside this — authentication and payment delegation are separate but adjacent flows.
This API handles card data and authentication outcomes. Implement it from the live spec, never from memory or an example found elsewhere.
Conceptual Architecture
What it delegates
Consumer authentication — specifically 3D Secure 2 browser-based flows — to a merchant-specified authentication provider. The agent does not perform 3DS itself; it drives a provider that does, and carries the result back into checkout.
Note the server in the spec is the authentication provider, not the seller. This is a distinct party from the merchant endpoints in acp-checkout-rest.
Endpoints
| Method | Path | Operation |
|---|---|---|
POST |
/delegate_authentication |
createAuthenticationSession — 201 |
POST |
/delegate_authentication/{authentication_session_id}/authenticate |
authenticateSession |
GET |
/delegate_authentication/{authentication_session_id} |
getAuthenticationSession |
Session statuses
| Status | Meaning |
|---|---|
action_required |
The provider needs a browser-side action performed — see below |
pending |
In progress; no action needed from the caller yet |
not_supported |
The card is not enrolled in 3DS |
authenticated |
Authentication succeeded |
not_authenticated |
Authentication failed |
not_supported is not a failure. It means the card is not enrolled and the flow should continue without 3DS — treating it as a decline will reject good transactions.
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.
- 1mo ago First seen · 83 lines · 65 tokens per session scan A 22be7eb13506
acp-delegate-authentication is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (40 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,104 once invoked, about $0.0003 per session on Opus 5.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-09-15.
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.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
archestra-dev-testing
Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
managing-archestra-releases
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.
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.
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.