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 agentmods add skills/builderced/agent-skills/gdpr-data-protectionnpx skills add BuilderCed/agent-skills --skill gdpr-data-protectiongit clone --depth 1 https://github.com/BuilderCed/agent-skillsWrote 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/builderced/agent-skills/gdpr-data-protection)<a href="https://agentmods.dev/skills/builderced/agent-skills/gdpr-data-protection"><img src="https://agentmods.dev/badge/skills/builderced/agent-skills/gdpr-data-protection.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 | $0.00041 | $0.01361 |
| Opus 5 | $0.00020 | $0.00681 |
| Sonnet 5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
gdpr-data-protection 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 5d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDPR Data Protection
DISCLAIMER: This skill provides guidance only. It does not constitute legal advice. Always verify with a Data Protection Officer or legal professional.
When to Use
- Designing systems that process personal data
- Conducting a Data Protection Impact Assessment (DPIA)
- Creating Article 30 processing records
- Implementing data subject rights (access, deletion, portability)
- Evaluating legal bases for data processing
- Planning cross-border data transfers
Step 1: Identify Legal Basis (Article 6)
Every processing activity needs exactly one legal basis:
| Legal Basis | When to Use | Example |
|---|---|---|
| Consent (6.1.a) | User actively opts in, can withdraw anytime | Newsletter signup |
| Contract (6.1.b) | Processing necessary to fulfill a contract | Delivering purchased goods |
| Legal obligation (6.1.c) | Required by law | Tax record retention |
| Vital interests (6.1.d) | Protecting someone's life | Emergency medical data |
| Public interest (6.1.e) | Official authority or public task | Government services |
| Legitimate interest (6.1.f) | Balanced against data subject's rights | Fraud prevention, security |
Consent requirements: freely given, specific, informed, unambiguous, easy to withdraw.
Step 2: Data Minimization Checklist
Before collecting any personal data:
- Is this data necessary for the stated purpose?
- Can the purpose be achieved with less data?
- Can the data be anonymized or pseudonymized?
- Is the retention period defined and minimal?
- Are access controls in place (who can see what)?
Step 3: Article 30 Processing Record
Every controller must maintain a record of processing activities:
Processing Activity: [Name]
Controller: [Organization name, contact]
DPO Contact: [If applicable]
Purpose: [Specific, explicit purpose]
Legal Basis: [From Step 1]
Data Categories: [e.g., name, email, IP address]
Data Subjects: [e.g., customers, employees]
Recipients: [Who receives the data, including processors]
Third Country Transfers: [If any, with safeguard mechanism]
Retention Period: [Specific duration or criteria]
Security Measures: [Encryption, access control, etc.]
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.
- 5d ago First seen · 143 lines · 41 tokens per session scan A f7a081905f7f
gdpr-data-protection is a skill published in the GitHub repository BuilderCed/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,361 once invoked, about $0.0002 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-31.
Other skills, from other repositories
compliance-review
Build or review code for compliance with the EU AI Act, GDPR, the NIS2 Directive (EU 2022/2555), and secure-development (SSDLC) best practice. Three modes. REVIEW: audit a repo and produce an evidence-based gap analysis — triggers on "compliance review", "gap analysis", "NIS2 check", "is this repo GDPR compliant"…
legal-verify-experts
Liefert Empfehlungen fuer Fachanwaelte, Kanzleien und Verifizierungs-Tools zu einem Rechtsthema. Nutze diese Skill wenn /legal-verify aufgerufen wird ODER wenn der User nach einem "Anwalt fuer ...", "Kanzlei fuer ...", "Tool zur Pruefung von ..." fragt.
legal-audit-codebase
Fuehrt einen systematischen Rechts-Audit einer Codebase durch (DE/EU-Scope). Nutze diese Skill wenn /legal-audit aufgerufen wird ODER wenn der User eine Codebase auf DSGVO/UWG/AGB/DDG/AI-Act/BFSG/UrhG/NIS2-Probleme untersuchen lassen will.
legal-kb-lookup
Laedt gezielt Knowledge-Base-Chunks zu einem rechtlichen Thema. Nutze diese Skill wenn /legal-kb aufgerufen wird ODER wenn der User eine spezifische Rechtsinformation braucht (z.B. "Erklaer mir Cookie-Consent", "Was sagt Art. 30 DSGVO?", "Welche Urteile gibt es zu Google Fonts?").
legal-update-sources
Aktualisiert KB-Artikel gegen Primaerquellen. Nutze diese Skill wenn /legal-update aufgerufen wird ODER wenn ein KB-Artikel aelter als 90 Tage ist und im aktuellen Arbeitskontext verwendet wird.
complyant
Fast, token-efficient compliance answers with citations. Covers GDPR, AI Act, PECR, HIPAA, TCPA, FCA rules, CAN-SPAM, CCPA, and more. Use when you need to know what regulations say about data, marketing, AI, financial services, or communications.