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 fmflurry/settings-opencode --skill gdpr-compliancegit clone --depth 1 https://github.com/fmflurry/settings-opencodeWrote 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/fmflurry/settings-opencode/gdpr-compliance)<a href="https://agentmods.dev/skills/fmflurry/settings-opencode/gdpr-compliance"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/gdpr-compliance/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/fmflurry/settings-opencode/gdpr-compliance"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/gdpr-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 210 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 72 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 131 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00088 | $0.10096 |
| Opus 5.5 | $0.00035 | $0.04038 |
| Sonnet 5.5 | $0.00018 | $0.02019 |
| Haiku 4.5 | $0.00009 | $0.01010 |
Grade A, and why
gdpr-compliance 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.
How it starts
The opening of the file, as written. The whole thing — 656 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDPR Compliance Reference & Code Audit Checklist
FRANCE / CNIL-Focused Edition
This skill provides foundational GDPR knowledge, actionable CNIL compliance requirements, and a concrete code-audit checklist for auditing data-protection compliance in French companies. Reference this alongside the gdpr-specialist agent when reviewing code or building data-processing features.
Jurisdiction: France (EU member state); primary authority = CNIL (Commission Nationale de l'Informatique et des Libertés). Supplementary French law: Loi n°2018-493 (Code de la Protection des Données Personnelles); French Penal Code (Art. 226-16 to 226-24).
Legal Disclaimer: This is informational guidance, not legal advice. For jurisdiction-specific requirements or contested interpretations, consult a DPO, legal counsel, or CNIL (Phone: +33 1 53 73 22 22; Web: https://www.cnil.fr/).
1. Applicability
GDPR applies to:
- Any organization (any size, any industry) established in France/EU OR targeting EU residents
- Processing of both computerized AND paper data
- Any personal data (Art. 4(1)): any information relating to an identified or identifiable natural person
French Supplementary Law:
- Loi Informatique et Libertés (Art. 82 onwards): cookie/tracker consent rules (stricter than GDPR baseline)
- French Penal Code (Art. 226-16 to 226-24): criminal penalties for unauthorized processing, failure to inform, misuse of personal data
2. Six Core GDPR Principles (Art. 5) + Accountability (Art. 5(2))
| Principle | Requirement | Code Implication | Citation |
|---|---|---|---|
| Lawfulness (Art. 5(1)(a)) | One of 6 legal bases required (Art. 6) | Document which basis applies to each processing; enforce authorization checks in code | gdpr-info.eu/art-5-gdpr |
| Fairness (Art. 5(1)(a)) | Processing not deceptive/discriminatory | Audit ML models for bias; transparent data use | gdpr-info.eu/art-5-gdpr |
| Transparency (Art. 5(1)(a)) | Inform data subjects of collection, purpose, rights | Implement privacy notices, consent dialogs, data-subject-rights endpoints | gdpr-info.eu/art-5-gdpr |
| Purpose Limitation (Art. 5(1)(b)) | Data used only for stated purpose; repurposing needs fresh legal basis | Enforce audit logging; segregate use-case logic; don't share data across purposes without reconsent | gdpr-info.eu/art-5-gdpr |
| Data Minimization (Art. 5(1)(c)) | Collect only strictly necessary data | Remove unused fields; set default to minimal; challenge every PII field added | gdpr-info.eu/art-5-gdpr |
| Accuracy (Art. 5(1)(d)) | Keep data accurate & up-to-date | Provide rectification endpoint (PATCH /api/subject/data/{field}); flag stale data for user review | gdpr-info.eu/art-5-gdpr |
| Storage Limitation (Art. 5(1)(e)) | Define retention periods upfront; delete when objective met | Implement TTL/retention schema in database; automated deletion jobs; cleanup migrations | gdpr-info.eu/art-5-gdpr |
| Integrity & Confidentiality (Art. 5(1)(f)) | Proportional technical + organizational security measures | Encryption (TLS, at-rest), access control, logging, incident response, staff training | gdpr-info.eu/art-5-gdpr |
| Accountability (Art. 5(2)) | Demonstrate compliance with all principles above | Maintain Register of Processing Activities (RoPA); conduct DPIAs; document legal bases; keep audit trails (code-enforceable via logging, retention schema comments, consent records) | gdpr-info.eu/art-5-gdpr |
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.
- 1mo ago First seen · 656 lines · 88 tokens per session scan A 0d7557958ebc
gdpr-compliance is a skill published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 10,096 once invoked, about $0.0004 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-08-30.
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.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
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.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…