eu-gdpr

eu-gdpr is a skill for Claude Code from VandanaAjayDubey111/great-pm. It costs 49 tokens per session (1,731 once invoked), scanned A, original, MIT.

A product-focused guide to the European Union's General Data Protection Regulation, or GDPR, the main EU privacy law. It covers lawful processing, consent, impact assessments, automated decisions, data requests, data location, children's data, and data-protection officers.

In plain words
What is it for?
Use it to review consent flows, privacy impact assessments, automated decisions, data requests, data residency, children's privacy, and data-protection responsibilities.
Why use it?
It helps product teams recognise privacy duties while designing and operating a service. This reduces the risk of collecting or using personal data without the required basis and safeguards.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

Part of the great-pm plugin — 114 skills, 34 commands, 48 agents, 5 hooks shipped together

Good fit Use it to review consent flows, privacy impact assessments, automated decisions, data requests, data residency, children's privacy, and data-protection responsibilities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vandanaajaydubey111/great-pm/eu-gdpr
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 VandanaAjayDubey111/great-pm --skill eu-gdpr
Clone the repo
git clone --depth 1 https://github.com/VandanaAjayDubey111/great-pm

Made for: Claude Code.

Or install great-pm, the plugin that ships this one along with the rest of its 114 skills, 34 commands, 48 agents, 5 hooks.

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 eu-gdpr

README.md
[![agentmods](https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/eu-gdpr/github.svg)](https://agentmods.dev/skills/vandanaajaydubey111/great-pm/eu-gdpr)
Your own site
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/eu-gdpr"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/eu-gdpr/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 eu-gdpr

Your own site · 80×15
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/eu-gdpr"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/eu-gdpr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,731 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.00049 $0.01731
Opus 5.5 $0.00020 $0.00692
Sonnet 5.5 $0.00010 $0.00346
Haiku 4.5 $0.00005 $0.00173

Measured 1mo ago against content hash bd624a698c23, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

eu-gdpr 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 1mo 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.

plugins/great-pm/skills/eu-gdpr/SKILL.md · 165 lines

How it starts

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

Codex host binding

  • Treat references to Claude slash workflows as the equivalently named Codex skill.
  • Before delegating to any specialist, read the great-pm-runtime skill and the selected packaged role file.
  • Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex spawn_agent call with that role and a bounded assignment.
  • For the spawn tool's task_name or agent_name identifier, replace canonical role-name hyphens with underscores (query-refiner-pm → query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
  • Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
  • If spawn_agent is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
  • Resolve bundled paths from the installed GreatPM plugin root.
  • Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
  • Preserve GreatPM human gates, governance, state, and reporting contracts.

EU GDPR — product-side playbook

GDPR isn't legal-only homework — it shapes product. Lawful basis dictates data flows, Article 22 affects AI-decision UX, DPIA is mandatory for high-risk processing. Treating GDPR as a Phase 2 retrofit produces unshippable products in the EU.

1. The 6 lawful bases — pick exactly one per processing activity

Basis When to use Risk
Consent User actively agrees; freely-given, specific, informed Easy to do wrong; consent fatigue
Contract Necessary to perform the contract user requested Misused for "we want to"
Legal obligation Required by law Narrow; cite the specific law
Vital interests Life-or-death Very narrow
Public task Public-sector only N/A for most fintechs
Legitimate interests Your interest, balanced against user's rights The "we have a good reason" basis; needs balancing test (LIA)

Read the full file on GitHub · 165 lines

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. 1mo ago First seen · 165 lines · 49 tokens per session scan A bd624a698c23

Subscribe to this mod's changes

eu-gdpr is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,731 once invoked, about $0.0002 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-21.