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-logginggit 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-logging)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wc-logging"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wc-logging/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-logging"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wc-logging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.01999 |
| Opus 5 | $0.00046 | $0.01000 |
| Sonnet 5 | $0.00018 | $0.00400 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
wc-logging 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 7d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WooCommerce logging
Use WooCommerce's shared logger for operational diagnostics that merchants can inspect in WooCommerce Status logs. Logs are disposable observability data, never the only record that a payment, migration, export, or webhook completed.
Basic pattern
$logger = wc_get_logger();
$logger->info(
'Order export queued.',
array(
'source' => 'myplugin-export',
'order_id' => $order_id,
'correlation_id' => $correlation_id,
'attempt' => $attempt,
)
);
Always set a stable, plugin-prefixed source. Current file logging sanitizes it and expects at least three characters. Do not generate one source per order, user, request, or date; that fragments log browsing and creates excessive files/source records.
Levels
| Level | Use |
|---|---|
debug |
Detailed development diagnostics; high volume and normally thresholded in production |
info |
Normal lifecycle milestones useful for operations |
notice |
Significant but expected condition |
warning |
Recoverable anomaly, fallback, retry, deprecation, or degraded behavior |
error |
Operation failed but the application remains usable |
critical |
A component or important workflow is unavailable |
alert |
Immediate operator action is required |
emergency |
Store/system is unusable |
Use the level methods (debug(), info(), warning(), error()) or log(). WC_Logger::add() is legacy and explicitly not the preferred API.
WooCommerce can disable logging globally and can set a minimum severity threshold. In 11.0.0 the default threshold is none, meaning all levels are accepted, but site settings or WC_LOG_THRESHOLD can change that. Never make application correctness depend on a log entry being handled.
Structured context
Prefer a constant message plus small, allowlisted context:
$logger->error(
'Provider capture failed.',
array(
'source' => 'myplugin-gateway',
'order_id' => $order->get_id(),
'provider_reference' => myplugin_mask_reference( $provider_reference ),
'provider_code' => sanitize_key( $provider_code ),
'correlation_id' => $correlation_id,
)
);
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.
- 7d ago First seen · 183 lines · 91 tokens per session scan A ecd03f2130dd
wc-logging is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 12d ago), licensed MIT. It adds 91 tokens to every session and 1,999 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
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
comet-github-issue-triage
A read-only workflow for checking and classifying Comet GitHub Issues, which are reports or requests about a software project. It compares each report with the repository’s code, tests, configuration, installation behavior, and existing issues.
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.
comet-runtime-diagnose
A diagnostic procedure for Comet's hooks, installation, routing, platform support, generated runtime, and lifecycle behavior.
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance…