Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add OrcaQubits/agentic-commerce-skills-plugins/plugin install commerce-readinessWrote 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/readiness-audit)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/readiness-audit"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/readiness-audit/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/readiness-audit"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/readiness-audit.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.00097 | $0.01173 |
| Opus 5.5 | $0.00039 | $0.00469 |
| Sonnet 5.5 | $0.00019 | $0.00235 |
| Haiku 4.5 | $0.00010 | $0.00117 |
Grade A, and why
readiness-audit 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Commerce Readiness Audit
You score a live site's readiness for AI-agent commerce using the executable probes in this plugin, then turn every gap into a concrete fix wired to the skills in this marketplace.
Prerequisites
Python 3.8+ on PATH (python3 or python). The probes are stdlib-only
— no pip installs. If Python is missing, tell the user how to install it for
their platform and stop; don't degrade to guessing.
Inputs
Ask for these if not provided:
- URL — required.
https://shop.example.comor a bare host. - Deep mode — opt-in. Default probes send GET/OPTIONS (plus MCP
tools/list, a pure read).--deepadds POST probes: a demo-SKU checkout create against ACP and UCP, NLWeb/ask, and a delegate_payment validation call. These are discovery-shaped, but on a live merchant a created session can trigger inventory holds or abandoned-cart emails — ask before enabling deep mode, and prefer a staging host. - Scope — optional:
all(default) or module idsr1,r2,r4.
Process
1. Run the audit
python "${CLAUDE_PLUGIN_ROOT}/scripts/readiness_audit.py" <URL> --out report/
# deep, with user consent:
python "${CLAUDE_PLUGIN_ROOT}/scripts/readiness_audit.py" <URL> --deep --out report/
Outside Claude Code — or on a converted platform bundle where
${CLAUDE_PLUGIN_ROOT} is not set — substitute the path to the
commerce-readiness plugin directory; the scripts have no other
dependency on the harness.
Emit one progress line before running ("Probing — 6 modules…") and one after ("Scored N/W — writing report/READINESS.md"). The runner executes all modules in parallel; a full shallow run takes under a minute.
For a single module, run its probe directly:
python "${CLAUDE_PLUGIN_ROOT}/scripts/probe_transact.py" <URL> --json
2. Interpret — with the rubrics, not your impressions
Read report/score.json. For any module you need to explain, read its
rubric in audit/r{N}.md — the rubric documents what each sub-check means,
its N/A condition, and the fix path. The scripts are the source of truth
for weights; the rubrics for meaning.
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 · 109 lines · 97 tokens per session scan A 38885a60b505
readiness-audit is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,173 once invoked, about $0.0004 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.
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.
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…