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-affiliate-attributiongit 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-affiliate-attribution)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/acp-affiliate-attribution"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-affiliate-attribution/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-affiliate-attribution"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/acp-affiliate-attribution.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.00042 | $0.00675 |
| Opus 5 | $0.00021 | $0.00338 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
acp-affiliate-attribution 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Affiliate Attribution
Before writing code
Fetch live docs:
- Web-search
site:github.com agentic-commerce-protocol rfcs affiliate_attributionfor the affiliate attribution RFC - Fetch
https://developers.openai.com/commerce/specs/checkout/for how attribution integrates with checkout - Web-search
site:github.com agentic-commerce-protocol spec json-schema affiliatefor the schema
Conceptual Architecture
What Affiliate Attribution Does
ACP's affiliate attribution extension provides privacy-preserving affiliate tracking without cookies. It replaces traditional cookie-based tracking with structured tokens that respect buyer privacy while enabling fair commission attribution.
Key Properties
- Write-only — Attribution data is sent to the merchant but NEVER echoed back in responses. This prevents information leakage.
- Privacy-preserving — No third-party cookies, no cross-site tracking, no browser fingerprinting
- Token-based — Attribution uses opaque tokens rather than personally identifiable data
- Two attribution models: First-touch and last-touch
Attribution Models
| Model | Description |
|---|---|
| First-touch | Credit goes to the first affiliate that referred the buyer |
| Last-touch | Credit goes to the most recent affiliate before purchase |
How It Works
- Affiliate generates a tracking token (opaque identifier)
- When buyer clicks affiliate link, the agent receives the attribution token
- Agent includes first-touch attribution data on create (
POST /checkout_sessions) and last-touch attribution data on complete (POST /checkout_sessions/{id}/complete) - Merchant receives attribution and records it for commission processing
- Merchant NEVER returns attribution in responses (write-only)
Data Flow
Affiliate → Token → Agent → Checkout Session (attribution field) → Merchant
↓
Commission Processing
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 · 85 lines · 42 tokens per session scan A 8b41ec22779a
acp-affiliate-attribution is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 42 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.
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-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.