com-example-compliance-GdprService

com-example-compliance-GdprService is a cursor rule for Cursor from PIsberg/vibetags. It costs 213 tokens per session, scanned A, original, MIT.

GDPR rules for managing a user's personal data, including deletion and machine-readable export. GDPR is a European privacy law.

In plain words
What is it for?
Updating GdprService, exporting user data, deleting personal information from every connected store, and testing repeated deletion calls.
Why use it?
They help implement the user's rights to have personal data erased and transferred, while keeping repeated deletion safe.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Updating GdprService, exporting user data, deleting personal information from every connected store, and testing repeated deletion calls.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pisberg/vibetags/com-example-compliance-gdprservice
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.

Clone the repo
git clone --depth 1 https://github.com/PIsberg/vibetags

Made for: Cursor.

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 com-example-compliance-GdprService

README.md
[![agentmods](https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-compliance-gdprservice/github.svg)](https://agentmods.dev/rules/pisberg/vibetags/com-example-compliance-gdprservice)
Your own site
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-compliance-gdprservice"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-compliance-gdprservice/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 com-example-compliance-GdprService

Your own site · 80×15
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-compliance-gdprservice"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-compliance-gdprservice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 213 This file is loaded in full into every session.
When invoked 213 The same file — it is already loaded in full.
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.00213 $0.00213
Opus 5.5 $0.00085 $0.00085
Sonnet 5.5 $0.00043 $0.00043
Haiku 4.5 $0.00021 $0.00021

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

Security

Grade A, and why

com-example-compliance-GdprService 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.

examples/basic/.cursor/rules/com-example-compliance-GdprService.mdc · 25 lines

What it actually says

Rules for GdprService

Regulatory Compliance

  • Standard: GDPR

Rules for class GdprService

  • Clause: Art. 17
  • Description: Right to erasure — when invoked, deletes ALL PII for the given user across every connected store.

Rules for method exportUserData

  • Clause: Art. 20
  • Description: Right to data portability — exports the user's data in a machine-readable format.

Rules for method deleteAllUserData

  • Rule: This operation is idempotent. Calling it multiple times must produce the same result as calling it once.
  • Reason: Deleting a user's data multiple times must produce the same result as deleting once — must not throw on second invocation.
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 Changed · +213 tokens per session 65bfff6cea7c
  2. 1mo ago First seen · 25 lines · 0 tokens per session scan A cb276b1d8a09

Subscribe to this mod's changes

com-example-compliance-GdprService is a cursor rule published in the GitHub repository PIsberg/vibetags (25 stars, last pushed today), licensed MIT. It adds 213 tokens to every session, about $0.0009 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.