cookie-auditor

cookie-auditor is a skill for Claude Code from ncklrs/claude-chrome-user-testing. It costs 0 tokens per session (1,908 once invoked), scanned A, original, MIT.

A web-page checker for cookie consent under GDPR, the European Union privacy law, and CCPA, the California privacy law. It starts with a clean browser session, records cookies before consent, and classifies them by purpose.

In plain words
What is it for?
Use it to audit cookie banners and consent behavior for GDPR or CCPA requirements, including checks in a CI/CD deployment process.
Why use it?
It reveals cookies or tracking activity that may happen before a visitor gives consent. This supports privacy checks before launch, during deployment, or when reviewing third-party vendors.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the user-testing-agent plugin — 14 skills, 10 commands shipped together

Good fit Use it to audit cookie banners and consent behavior for GDPR or CCPA requirements, including checks in a CI/CD deployment process.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ncklrs/claude-chrome-user-testing/cookie-auditor
Install

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.

Any agent
npx skills add ncklrs/claude-chrome-user-testing --skill cookie-auditor
Clone the repo
git clone --depth 1 https://github.com/ncklrs/claude-chrome-user-testing

Made for: Claude Code.

Or install user-testing-agent, the plugin that ships this one along with the rest of its 14 skills, 10 commands.

Wrote 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.

agentmods badge for cookie-auditor

README.md
[![agentmods](https://agentmods.dev/badge/skills/ncklrs/claude-chrome-user-testing/cookie-auditor/github.svg)](https://agentmods.dev/skills/ncklrs/claude-chrome-user-testing/cookie-auditor)
Your own site
<a href="https://agentmods.dev/skills/ncklrs/claude-chrome-user-testing/cookie-auditor"><img src="https://agentmods.dev/badge/skills/ncklrs/claude-chrome-user-testing/cookie-auditor/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.

agentmods 80×15 button for cookie-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/ncklrs/claude-chrome-user-testing/cookie-auditor"><img src="https://agentmods.dev/badge/skills/ncklrs/claude-chrome-user-testing/cookie-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,908 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01908
Opus 5 $0.00000 $0.00954
Sonnet 5 $0.00000 $0.00382
Haiku 4.5 $0.00000 $0.00191

Measured 9d ago against content hash 9b50355c5445, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cookie-auditor 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.

skills/cookie-auditor/SKILL.md · 308 lines

How it starts

The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Audit web pages for GDPR and CCPA cookie consent compliance.

When to Use

  • Verifying GDPR compliance before EU launch
  • Checking CCPA compliance for California users
  • Pre-deployment privacy compliance checks
  • Auditing third-party vendors' consent implementation
  • CI/CD compliance gates

Audit Approach

Phase 1: Fresh Session Setup

Start with a clean browser state:

// Via browser_run_code
async (page) => {
  // Clear all cookies
  await page.context().clearCookies();

  // Clear local storage
  await page.evaluate(() => {
    localStorage.clear();
    sessionStorage.clear();
  });

  return 'Session cleared';
}

Phase 2: Pre-Consent Cookie Capture

Before any interaction, record what cookies are set:

async (page) => {
  const cookies = await page.context().cookies();
  return cookies.map(c => ({
    name: c.name,
    domain: c.domain,
    path: c.path,
    expires: c.expires,
    httpOnly: c.httpOnly,
    secure: c.secure,
    sameSite: c.sameSite
  }));
}

Phase 3: Cookie Classification

Classify cookies by purpose:

Pattern Category Essential
session, csrf, auth Necessary Yes
_ga, _gid, analytics Analytics No
_fbp, _gcl, ads Marketing No
prefs, theme, lang Personalization No

Phase 4: Banner Detection

Look for cookie consent elements:

// Common selectors for cookie banners
const bannerSelectors = [
  '[class*="cookie"]',
  '[id*="cookie"]',
  '[class*="consent"]',
  '[id*="consent"]',
  '[class*="gdpr"]',
  '[class*="privacy-banner"]',
  '[aria-label*="cookie"]',
  '[role="dialog"][class*="modal"]'
];

Phase 5: Consent Mechanism Analysis

Check consent UI for compliance:

Accept Button Detection:

const acceptSelectors = [
  'button:has-text("Accept")',
  'button:has-text("Allow")',
  'button:has-text("Agree")',
  'button:has-text("OK")',
  '[class*="accept"]'
];

Read the full file on GitHub · 308 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 9d ago First seen · 308 lines · 0 tokens per session scan A 9b50355c5445

Subscribe to this mod's changes

cookie-auditor is a skill published in the GitHub repository ncklrs/claude-chrome-user-testing (19 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,908 tokens. 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-08-30.

Related

Other skills, from other repositories

policy-creation

Guide for adding new enterprise policies to Chromium. Complete guide for policy definitions, pref mapping, and writing tests.

chromium/chromium · 26 tokens

web-quality-audit

Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

addyosmani/web-quality-skills · 58 tokens

open-computer-use

Platform-neutral guidance for using Open Computer Use, the open-source Computer Use MCP server and CLI for macOS, Linux, and Windows. Use when an agent needs to install, verify, troubleshoot, configure, or operate Open Computer Use through its native CLI, stdio MCP server, or direct Computer Use tool calls.

iFurySt/open-codex-computer-use · 68 tokens

privacy

Action-oriented guidelines for privacy by design, data minimization, third-party audits, and modern browser privacy APIs. Use this skill when dealing with user data, cookies, tracking, third-party scripts, or browser privacy APIs.

GoogleChrome/modern-web-guidance-src · 46 tokens

macos-harness

Control a whole Mac from one persistent Python session with screenshots, PID-targeted input, an animated virtual pointer, targeted Apple Accessibility, Apple Events, Browser Harness CDP, and filesystem access. Use for native, Electron, browser, dialog, file, or cross-app tasks without moving the physical cursor or…

browser-use/macos-harness · 71 tokens

legal-iros-registry-automation

A guide for helping automate bulk requests for company or property registry certificates from South Korea’s Supreme Court Internet Registry Office (IROS). The user handles login, authentication, and payment in the browser, while the workflow assists with collecting, saving, and reporting the documents.

modu-ai/moai-cowork · 310 tokens