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 Lonsdale201/wp-agent-skills --skill wc-extension-upgrade-auditgit clone --depth 1 https://github.com/Lonsdale201/wp-agent-skillsWrote 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/lonsdale201/wp-agent-skills/wc-extension-upgrade-audit)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wc-extension-upgrade-audit"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wc-extension-upgrade-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/lonsdale201/wp-agent-skills/wc-extension-upgrade-audit"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wc-extension-upgrade-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.00101 | $0.01079 |
| Opus 5 | $0.00051 | $0.00540 |
| Sonnet 5 | $0.00020 | $0.00216 |
| Haiku 4.5 | $0.00010 | $0.00108 |
Grade A, and why
wc-extension-upgrade-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 9d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WooCommerce extension upgrade audit
Use this skill to produce evidence for compatibility, not merely to change a version header. Changelogs identify likely areas; installed release source and runtime behavior establish the contract actually shipped.
When the audit crosses from WooCommerce 10.9 or older to 11.0 or newer, read references/woocommerce-11.md before changing code.
Workflow
1. Establish exact baselines
Record:
- source and target WooCommerce versions;
- WordPress and PHP versions;
- active HPOS, block checkout, email, fulfillment, and experimental feature states;
- bundled/active Action Scheduler version;
- companion extensions in scope, such as Stripe or Subscriptions.
Do not infer the runtime Action Scheduler version from WooCommerce's bundled directory alone. WordPress loads the newest registered copy.
2. Inventory the extension's contracts
Search its PHP, JavaScript, templates, tests, and build metadata for:
- Woo hooks and filters, including accepted argument counts;
- Woo CRUD classes, data stores, direct meta access, custom SQL, and internal namespaces;
/wc/v3,/wc/v4,/wc/store/v1, AJAX, andwc-ajaxconsumers;- template overrides and copied JS/CSS handles;
- feature IDs and raw option checks;
- product/order taxonomies and queried-object assumptions;
- Action Scheduler uniqueness, status, cleanup, and CLI assumptions;
- Checkout Blocks payment method registration and
@woocommerce/*package contracts.
Classify each dependency as public documented API, public hook, de facto legacy surface, internal API, or copied implementation detail. Internal namespace use is an upgrade risk even if it still exists.
3. Diff behavior, not filenames
Compare the exact old and new release source around every inventoried contract. Check:
- hook position, argument order, return semantics, and whether persistence occurs before or after the hook;
- route method, permission callback, schema, defaults, normalization, and error status;
- default feature state for new installs versus upgraded stores;
- template version headers and required DOM/data attributes;
- cache invalidation and object lifetime;
- bundled-library semantic changes.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 96 lines · 101 tokens per session scan A 3e072217c8a3
wc-extension-upgrade-audit is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 101 tokens to every session and 1,079 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
testing-and-go-live
Guide for test-mode payment scenarios, renewal simulation, local webhook delivery tests, test and live catalog migration, and production launch checks.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
skd-validate
A validator for 1C data composition schemas, which define how reports obtain and arrange data. It checks a Template.xml file for structural errors, broken references, and duplicate names.