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 HermeticOrmus/LibreSecOps-Claude-Code --skill gdpr-requirementsgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/gdpr-requirements)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/gdpr-requirements"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/gdpr-requirements.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.1 | $0.00000 | $0.02724 |
| Opus 5 | $0.00000 | $0.01362 |
| Sonnet 5 | $0.00000 | $0.00545 |
| Haiku 4.5 | $0.00000 | $0.00272 |
Grade A, and why
gdpr-requirements 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 7d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDPR Requirements
GDPR compliance patterns for technology organizations covering data processing principles, data subject rights, technical and organizational measures, and breach notification.
Knowledge Base
GDPR Overview
The General Data Protection Regulation (EU 2016/679) is the European Union's data protection law. It applies to any organization that processes personal data of individuals in the EU/EEA, regardless of where the organization is located. Non-compliance can result in fines up to 20 million EUR or 4% of global annual turnover, whichever is higher.
Key Definitions
| Term | Definition |
|---|---|
| Personal data | Any information relating to an identified or identifiable natural person (data subject). Includes: name, email, IP address, location data, cookie identifiers, health data, biometric data. |
| Processing | Any operation performed on personal data: collection, storage, use, transmission, erasure, and everything in between. |
| Controller | The entity that determines the purposes and means of processing. (Your organization, if you decide what data to collect and why.) |
| Processor | The entity that processes data on behalf of the controller. (Your cloud provider, email service, analytics provider.) |
| Data subject | The individual whose personal data is being processed. |
| DPA | Data Protection Authority -- the regulatory body that enforces GDPR in each EU member state. |
| DPO | Data Protection Officer -- required for certain organizations (Article 37). |
Article 5: Data Processing Principles
These seven principles are the foundation of GDPR. Every processing activity must comply with all of them.
1. Lawfulness, Fairness, and Transparency
- Processing must have a lawful basis (Article 6)
- Data subjects must be informed about how their data is processed
- Privacy policy must be clear, accessible, and written in plain language
- No hidden data collection or processing
Implementation: Privacy policy, cookie consent, clear data collection notices, Records of Processing Activities (ROPA).
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.
- 7d ago First seen · 236 lines · 0 tokens per session scan A 029215d9a891
gdpr-requirements is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,724 tokens. 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
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
collecting-volatile-evidence-from-compromised-host
Collect volatile forensic evidence from a compromised system following order of volatility, preserving memory, network connections, processes, and system state before they are lost.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…