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.
git clone --depth 1 https://github.com/ncklrs/claude-chrome-user-testingWrote 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/commands/ncklrs/claude-chrome-user-testing/cookie-audit)<a href="https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/cookie-audit"><img src="https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/cookie-audit.svg" alt="Measured on agentmods" 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.00029 | $0.02458 |
| Opus 5 | $0.00015 | $0.01229 |
| Sonnet 5 | $0.00006 | $0.00492 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
cookie-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 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cookie Audit Command
Perform a comprehensive cookie consent compliance audit to identify GDPR and CCPA violations and generate an actionable report.
Arguments
Parse the following from $ARGUMENTS:
--url <url>(required): URL to audit--regulation <gdpr|ccpa|both>(optional): Target regulation (default: both)--format <format>(optional): Output format - summary | detailed | json (default: detailed)--save <filename>(optional): Save report to file--annotate(optional): Take annotated screenshots of violations
Prerequisites
This command requires:
- Claude running with
--chromeflag - Playwright MCP tools available
Audit Flow
Step 1: Initialize
- Clear browser cookies/storage to simulate fresh visit
- Navigate to the target URL using
browser_navigate - Record what cookies are set BEFORE any user interaction
- Take initial snapshot with
browser_snapshot - Look for cookie consent banner
Step 2: Pre-Consent Cookie Check
Before interacting with any consent mechanism:
Use browser_run_code to check cookies:
async (page) => {
const cookies = await page.context().cookies();
return cookies.map(c => ({
name: c.name,
domain: c.domain,
category: classifyCookie(c.name) // analytics, marketing, necessary
}));
}
Record any non-essential cookies set before consent.
Step 3: Run GDPR Checks (if --regulation gdpr or both)
Check these GDPR cookie consent requirements:
GDPR-1: Banner Before Cookies (Critical)
Check: Non-essential cookies should not be set before consent
Pass: Only necessary cookies exist on initial load
Fail: Analytics/marketing cookies present before any interaction
Severity: Critical
GDPR-2: No Pre-Checked Boxes (Critical)
Check consent form for pre-checked options:
- Marketing cookies checkbox
- Analytics cookies checkbox
- Personalization checkbox
Use browser_snapshot to find:
- Checkboxes in consent banner
- Default checked state
Severity: Critical
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 · 413 lines · 29 tokens per session scan A 49a2dcd0a7d0
cookie-audit is a command published in the GitHub repository ncklrs/claude-chrome-user-testing (19 stars, last pushed 8mo ago), licensed MIT. It adds 29 tokens to every session and 2,458 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
snr-privacy
Build the privacy pack — data inventory from the code, an accurate privacy policy, working cookie consent, and an automated self-service deletion pipeline.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.