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 ThomasMoreAI/legal-skills-open --skill cookie-consent-policygit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/cookie-consent-policy)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/cookie-consent-policy"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/cookie-consent-policy/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/thomasmoreai/legal-skills-open/cookie-consent-policy"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/cookie-consent-policy.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.00096 | $0.01446 |
| Opus 5 | $0.00048 | $0.00723 |
| Sonnet 5 | $0.00019 | $0.00289 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
cookie-consent-policy 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cookie Consent Banner and Policy
Drafts an enforceable cookie policy and compliant banner framework from a verified cookie inventory and jurisdiction scope.
Prerequisites
- Site inventory — all domains, subdomains, in-app endpoints
- Cookie/SDK inventory — names, hosts, providers, purpose, category, retention, data-sharing paths
- Jurisdiction scope — EU/EEA applicability, California residents, other state-law coverage
- Consent design — banner UI behavior, consent states, defaults, expiration/renewal, withdrawal path
- Contacts — privacy contact, DPO (if required), external processors, complaint channels
Step 1: Collect Inputs
Gather all inputs; apply and label defaults if user says "use defaults."
| Input | Required | Default if missing |
|---|---|---|
| Jurisdictions served | yes | US + EU |
| Cookie inventory | yes | [VERIFY] — complete inventory required |
| Consent mechanism | yes | banner + preference center |
| User rights contact | yes | privacy@ [CLIENT TO SPECIFY] |
| Update cadence | yes | 6–12 months + material-change notices |
Step 2: Draft Policy Sections
Generate in this order:
| Section | Mandatory fields | EU/US notes |
|---|---|---|
| Purpose & scope | organization, websites, users affected, last-updated date | include EEA processing basis and non-EU logic |
| What are cookies | definition + non-cookie trackers (pixels, web beacons, local storage) | examples required |
| Cookie categories | strict table by category (see Step 3) | essential cookies exempt from consent where lawful |
| How we use cookies | purpose + legal basis + processors/recipients | map each non-essential use to explicit consent |
| Your choices | accept all / reject non-essential / customize | no bundling consent with account creation |
| Managing preferences | withdrawal and edits anytime | explain functional limits if opt-outs selected |
| Rights | GDPR, CCPA/CPRA, state-law rights | include agency contact + complaint route |
| Changes | versioning + notice method + effective date | material changes require renewed consent |
| Contact | email/portal/address + response SLA | U.S. and EU contact as applicable |
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.
- 9d ago First seen · 116 lines · 96 tokens per session scan A c2504fddc820
cookie-consent-policy is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (72 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,446 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
Compliance Gap Matrix
Use when mapping a set of regulatory or framework requirements against an organization's current controls to surface gaps, prioritize remediation, and produce an attorney-ready draft gap analysis.
Compliance Program Tracker
Use when building an ongoing compliance-program tracker for a framework — mapping requirements to controls, owners, and evidence, building an audit calendar, and surfacing evidence gaps and remediation items for attorney review and audit readiness.
pia-generator
Generate structured privacy impact assessments so Claude can organize project privacy risks, controls, and decision points into a review-ready report.
audit-scope-checklist
Generate a scoped IT audit program with controls mapped to roles and compliance frameworks. Use this skill for audit planning, control checklist generation, and auditprogram.json creation.
compliance-checker
Compare system configuration evidence against common control frameworks and produce a concise compliance assessment with gaps and remediation priorities.
compliance-controls-playbook
Guide Claude through a structured compliance audit workflow covering framework selection, evidence planning, control testing, exception handling, and reporting.