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 joao-aires/agent-skills-public --skill gdpr-readinessgit clone --depth 1 https://github.com/joao-aires/agent-skills-publicWrote 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/joao-aires/agent-skills-public/gdpr-readiness)<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/gdpr-readiness"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/gdpr-readiness/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/joao-aires/agent-skills-public/gdpr-readiness"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/gdpr-readiness.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.00046 | $0.00743 |
| Opus 5.5 | $0.00018 | $0.00297 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
gdpr-readiness 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 yesterday.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess the actual processing operation
Establish the service, entities, people affected, purposes, categories/sensitivity, locations and provider/data flows. Determine which processing operation is being assessed and whether the organization's role differs across customer data, account administration, analytics or model/provider use. Preserve accepted interpretations and distinguish facts from unresolved legal judgments. Read applicability and system decisions for conditional concerns and official sources when determining substantive requirements.
Establish applicability from facts
Consider establishment and relevant offering/monitoring activity, not just server location, nationality or the product being commercial.
- Establish controller/processor roles from actual purposes/means and relationships; do not infer that every SaaS vendor is always only a processor.
- Record material uncertainties and seek the appropriate legal/business interpretation when required.
- Assess relevant national/sectoral and ePrivacy requirements separately where the actual feature raises them.
For each processing purpose, establish the accepted basis, necessary data, transparency and retention.
Consent is not a universal fallback and a privacy notice does not establish a lawful basis.
When processing raises additional concerns
Check special-category/children's data, profiling or other elevated-impact processing when present. Investigate whether a DPIA or other responsibility applies; neither impose one for every feature nor silently omit it.
Translate requirements into the system lifecycle
Follow each assessed processing purpose through the actual data lifecycle. Identify where data first enters, which people and services can access it, what it is used for, and which copies or derived forms are created. Include logs/analytics, AI/provider requests, exports and recovery paths, since these can continue processing data outside the main application record.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 56 lines · 46 tokens per session scan A 5ad37b8a93f1
gdpr-readiness is a skill published in the GitHub repository joao-aires/agent-skills-public (2 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 743 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-10-21.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.