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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/legal-rgpd)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/legal-rgpd"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-rgpd/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/commands/christopherlouet/claude-base/legal-rgpd"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-rgpd.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.00000 | $0.00341 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
legal-rgpd 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.
What it actually says
GDPR Agent
GDPR compliance audit of a project.
Request context
$ARGUMENTS
Objective
Analyze the codebase to identify the personal data collected, verify GDPR compliance and propose a prioritized action plan.
Workflow
- Scan the code to identify personal data (email, phone, IP, etc.)
- Map data flows (collection, storage, transmission)
- Verify the legal basis of each processing (Art. 6)
- Audit consent and cookies (banner, blocking, dark patterns)
- Verify the implementation of data subject rights (access, rectification, erasure, portability)
- Analyze retention periods and purge mechanisms
- Identify transfers outside the EU and the safeguards
- Verify data security (encryption, hashing, RBAC)
- Generate the draft of the processing register (Art. 30)
Expected output
- Compliance summary with estimated level
- Personal data identified with location and legal basis
- Compliance by domain (consent, rights, retention, transfers, security)
- Critical non-compliance with recommendations
- Action plan prioritized
Related agents
| Agent | Usage |
|---|---|
/legal:legal-docs |
Complete legal documents |
/legal:legal-privacy-policy |
Privacy policy |
/qa:qa-security |
Data security |
IMPORTANT: This audit is a technical analysis of the code. It does not replace legal advice.
YOU MUST identify all personal data flows, including to third-party services.
NEVER consider that a popular service is automatically GDPR-compliant.
Think hard about the data flows and risks before concluding.
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 · 50 lines · 0 tokens per session scan A d4b1b00f5589
legal-rgpd is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 341 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-09-03.
Other commands, from other repositories
migrate
Generate and manage database migrations.
context-stats
Display context window usage and token statistics.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
cancel-ralph
Cancel active Ralph Wiggum loop.
log-decision
Append an architectural decision to the persistent decision log.
update-docs
Scan for recently modified files and update corresponding documentation.