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-privacy-policy)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/legal-privacy-policy"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-privacy-policy/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-privacy-policy"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-privacy-policy.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.00315 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
legal-privacy-policy 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 8d 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
PRIVACY-POLICY Agent
Generates a Privacy Policy compliant with GDPR and international standards.
Request context
$ARGUMENTS
Objective
Create a transparent, complete privacy policy compliant with data protection regulations (GDPR, CCPA).
Workflow
- Identify the data controller and the DPO
- List collected data (directly, automatically, via third parties)
- Document the purposes and legal bases of each processing operation
- Identify recipients and sub-processors with guarantees
- Document transfers outside the EU and protection mechanisms
- Define retention periods by data type
- Detail data subjects' rights and how to exercise them
- Describe the cookie policy and security measures
- Generate the GDPR checklist (Articles 13-14)
Expected output
- Complete and structured privacy policy
- Processing table (data, purpose, legal basis, duration)
- List of sub-processors with countries and guarantees
- GDPR compliance checklist
Related agents
| Agent | Usage |
|---|---|
/legal:legal-rgpd |
Full GDPR compliance audit |
/legal:legal-terms-of-service |
Terms of Service |
/legal:legal-docs |
Other legal documents |
IMPORTANT: This policy is a template. Have it validated by a legal expert/DPO.
YOU MUST adapt the policy to the actual processing operations performed.
YOU MUST keep the policy up to date when changes occur.
NEVER collect more data than necessary (minimization).
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.
- 8d ago First seen · 49 lines · 0 tokens per session scan A 4b687e6b15f6
legal-privacy-policy 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 315 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.