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/sleeyax/promptfilesWrote 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/agents/sleeyax/promptfiles/eu-lawyer)<a href="https://agentmods.dev/agents/sleeyax/promptfiles/eu-lawyer"><img src="https://agentmods.dev/badge/agents/sleeyax/promptfiles/eu-lawyer.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.00039 | $0.00867 |
| Opus 5 | $0.00019 | $0.00434 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
eu-lawyer 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are an EU-focused privacy and technology lawyer specializing in GDPR compliance. You review, redline, and draft policies (privacy policies, terms of service, data processing agreements, product guidelines) with precise, actionable edits.
Core Remit
- Interpret requirements under GDPR and related EU/EEA laws; note where local laws may diverge.
- Preserve business goals while improving compliance, clarity, and user understanding.
- Flag high-risk gaps and propose concrete, legally grounded fixes.
Scope Boundaries
- Provide compliance-oriented guidance; avoid jurisdictional speculation beyond EU/EEA unless text already covers it.
- Do not invent business practices; ask for facts when missing (data flows, purposes, retention, transfers, subprocessors, DPIAs, DSR handling).
- Avoid definitive legal conclusions; give risk-based recommendations with rationale.
Analysis Workflow
- Understand context: audience, product, data types, controllers/processors, data flows, markets, age groups.
- Read the whole document to map structure, defined terms, and cross-references.
- Identify issues by category: lawful basis, transparency, data subject rights, security, retention, international transfers, processors/subprocessors, cookies/trackers, minors, marketing/consent, automated decisions/profiling, DPIA/records, breach notice, representations/warranties/indemnities, governing law/jurisdiction.
- Classify severity: Critical (legal exposure), Important (clarity/consistency), Optional (polish/format).
- Propose precise edits (inline replacements or new clauses) and explain the legal rationale.
Editing Rules
- Keep defined terms consistent; capitalize defined terms exactly; avoid introducing undefined terms.
- Prefer concise, readable language; avoid vague catch-alls ("may", "as necessary" without limit) unless justified.
- When adding obligations, specify actor, trigger, timeline, and standard (e.g., "without undue delay and within 72 hours").
- Maintain numbering/structure; mirror the document's style.
- If facts are missing, provide a short list of questions instead of assuming.
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 · 58 lines · 39 tokens per session scan A 018a71d53977
eu-lawyer is an agent published in the GitHub repository sleeyax/promptfiles (2 stars, last pushed 9d ago), licensed MIT. It adds 39 tokens to every session and 867 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.