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 readiness-fix-plangit 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/readiness-fix-plan)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/readiness-fix-plan"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/readiness-fix-plan/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-fix-plan"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/readiness-fix-plan.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.00077 | $0.00825 |
| Opus 5.5 | $0.00031 | $0.00330 |
| Sonnet 5.5 | $0.00015 | $0.00165 |
| Haiku 4.5 | $0.00008 | $0.00082 |
Grade A, and why
readiness-fix-plan 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Readiness Fix Plan
You turn a score.json from readiness-audit into a plan a team can
execute. The audit says what is broken; you decide order, owner-sized
chunks, and which skill does the work.
Inputs
report/score.json— required. If absent, runreadiness-auditfirst (or ask the user where their score.json lives).- Repo path — optional but changes the quality of the plan: with it you can name the actual framework and files; without it, hints stay generic.
- Format — plan in chat (default), and/or one issue block per gap ready to paste into a tracker.
Building the plan
- Read every module in score.json — statuses, failing sub-checks,
evidence strings,
fix_skillfields. The evidence strings are verbatim probe output; quote them, don't paraphrase. - Order by dependency first, priority second:
- An r1 blocker is always step 1 — nothing else is testable until agents can fetch.
- Discovery (r2) before transactability (r4): an endpoint nobody can find might as well not exist. Payment (r5) after checkout (r4).
- Within a tier, sort by
priority(already computed:impact × (6 − complexity)).
- Detect the stack if a repo path was given (package.json / Gemfile /
composer.json / requirements.txt), and route platform-shaped gaps to the
platform plugin: Product JSON-LD on a WooCommerce site is
woocommerce-commerce:woo-catalog, on Magentomagento2-commerce:magento-catalog— the genericfix_skillin score.json is the fallback, not the final answer. - Size each step — small (config/file drop: discovery docs, robots, llms.txt), medium (structured data, OAuth wiring), large (checkout endpoint, delegated payment). Flag the larges as projects, not tasks.
- State the projected score after the small+medium steps, computed from the actual weights in score.json — never estimated.
Plan format
| # | Fix | Module | Skill to invoke | Size | +pts |
|---|
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 · 68 lines · 77 tokens per session scan A 6d49080d4984
readiness-fix-plan is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 825 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.
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.…