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 lw-cookie-consent-integrationgit 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/lw-cookie-consent-integration)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/lw-cookie-consent-integration"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-cookie-consent-integration/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/lw-cookie-consent-integration"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-cookie-consent-integration.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.00116 | $0.02574 |
| Opus 5.5 | $0.00046 | $0.01030 |
| Sonnet 5.5 | $0.00023 | $0.00515 |
| Haiku 4.5 | $0.00012 | $0.00257 |
Grade A, and why
lw-cookie-consent-integration 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 19d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LW Cookie 1.8: consent integration and operations
Use LW Cookie's public hooks, browser API, REST routes, CLI, and abilities. Do not patch the plugin or infer legal compliance from a technical setting. Consent requirements depend on the site's processing, jurisdiction, vendor behavior, and legal basis.
Binding requirements and storage
Read the plugin header rather than old README badges:
| Contract | Version 1.8.3 |
|---|---|
| WordPress | 6.6 or newer |
| PHP | 8.2 or newer |
| Main option | lw_cookie_options |
| Categories | necessary, functional, analytics, marketing |
| Site Manager namespace | lw-cookie/* |
| Public shortcode | [lw_cookie_declaration] |
necessary is always required. The three optional categories default to denied until consent is saved.
Do not write lw_cookie_options directly. The admin REST settings controller and the 1.8.3 lw-cookie/set-options ability both use the sanitized partial-update path for field types, enums, colors, IDs, multilingual locks, and declared-cookie rows.
Read consent through the public filters
$categories = apply_filters( 'lw_cookie_consent_categories', [] );
$has_choice = apply_filters( 'lw_cookie_has_consent', false );
$analytics = apply_filters( 'lw_cookie_is_category_allowed', false, 'analytics' );
$consent_id = apply_filters( 'lw_cookie_consent_id', null );
Pass both documented arguments to lw_cookie_is_category_allowed. Treat an unknown category as denied.
These filters read the visitor's consent cookie. Do not let a full-page cache share consent-dependent HTML between visitors. A cache-safe integration renders the blocked form for everyone and lets the browser restore content after consent.
Browser API and event
Use the global API after the plugin's frontend assets load:
window.LWCookie.openPreferences();
window.LWCookie.acceptCategory( 'marketing' );
const state = window.LWCookie.getConsent();
const analyticsAllowed = window.LWCookie.isAllowed( 'analytics' );
window.addEventListener( 'lwCookieConsent', ( event ) => {
const categories = event.detail.categories;
const action = event.detail.action;
} );
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.
- 19d ago First seen · 215 lines · 116 tokens per session scan A efc58977840d
lw-cookie-consent-integration is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 19d ago), licensed MIT. It adds 116 tokens to every session and 2,574 once invoked, about $0.0005 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-27.
Other skills, from other repositories
azure-health-data-services
Expert knowledge for Azure Health Data Services development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using FHIR/DICOM APIs, bulk import/export, de-identification…
wp-plugin-development
Architecture and development guidelines for WordPress plugins published on wordpress.org: file structure, plugin header, lifecycle hooks, Settings API, admin UI, escaping helpers for admin JavaScript, default values and option migrations, translatable defaults, multisite-shared resources, short-circuit filters, custom…
wp-plugin-performance
Performance guidelines for WordPress plugin development: database optimization, object caching, conditional asset loading, efficient hooks, HTTP requests, WP-Cron, AJAX/REST optimization, and common anti-patterns. Based on official WordPress Developer Resources and WP VIP documentation.
compliance-rgi
Ensures system interoperability via open standards, documented APIs, and standardized data exchange.
data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the API. Don't use for implementing audience…
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.