cookie-tracker-audit
Skill1 starsChanged 41 days agoMITView on GitHub
Audit a website's cookies, trackers and third-party scripts for GDPR/ePrivacy compliance. Use when the user gives a URL or site source and asks about cookies, consent banners, analytics, pixels or tracking.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lolokauf/healthy-tension-privacy-skillstheir own version, first seen Mar 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lolokauf/healthy-tension-privacy-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- breach-responseSkill
- dpa-reviewSkill
- dpiaSkill
- dsar-responseSkill
- privacy-policy-reviewSkill
- ropaSkill
The file
Files
Cookie and tracker audit
- Collect evidence. For a URL, load it with a browser tool if available (or fetch the HTML) and list: cookies set, localStorage keys, third-party domains, scripts, iframes, pixels, fonts and embeds. For local source, grep for
gtag,analytics,fbq,pixel,hotjar,clarity,<script src=,<iframe,document.cookie,localStorage. Record what loads before any consent interaction separately from what loads after. - Classify each item: strictly necessary / preferences / statistics / marketing, with vendor and country of processing (flag non-EEA transfers).
- Check compliance (ePrivacy Art. 5(3), GDPR Arts. 6-7, EDPB/CNIL guidance):
- Non-essential items must not fire before opt-in.
- Banner offers Reject as easily as Accept; no pre-ticked boxes; no cookie walls.
- Granular choices per purpose; consent can be withdrawn as easily as given.
- Cookie policy lists each cookie, purpose, duration and vendor.
- Third-party embeds (YouTube, Maps, fonts) loaded without consent.
- Consent records kept; retention of cookies reasonable (typically <= 13 months).
- Report a table: item, category, fires pre-consent (Y/N), issue, fix. Then a prioritised fix list (High/Medium/Low).
State limits: a static check cannot prove behaviour after consent choices; say what was and was not tested. Working draft, not legal advice.
Edge cases
- Local source with no consent logic (or a banner whose buttons have no handlers): treat everything non-essential as firing pre-consent and say so.
- Include non-item rows (banner, missing cookie policy) with "n/a" in the pre-consent column; mark uncertain results "Y (probable)" and explain (e.g. broken or stubbed snippets).
- Country of processing: from source alone, state the vendor's known entity and mark transfers "likely US" rather than asserting; unknown items are "Unclassified".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.