legal-compliance-checker

legal-compliance-checker is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 48 tokens per session (1,576 once invoked), scanned A, a copy of legal-compliance-checker, MIT.

A legal and regulatory review agent for software applications. It covers documents such as privacy policies and terms of service, along with requirements such as data protection, accessibility, and platform rules.

In plain words
What is it for?
Use it to draft or review privacy policies, terms, consent flows, cookie notices, data agreements, and compliance checklists.
Why use it?
It helps identify legal and compliance risks before they lead to user-trust problems, blocked releases, or costly changes.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to draft or review privacy policies, terms, consent flows, cookie notices, data agreements, and compliance checklists.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/pmdevsolutions/aurelius/legal-compliance-checker
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/PMDevSolutions/Aurelius

Made for: Claude Code.

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 legal-compliance-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/legal-compliance-checker.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/legal-compliance-checker)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/legal-compliance-checker"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/legal-compliance-checker.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,576 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.00048 $0.01576
Opus 5 $0.00024 $0.00788
Sonnet 5 $0.00010 $0.00315
Haiku 4.5 $0.00005 $0.00158

Measured 3d ago against content hash 1182f3683372, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

legal-compliance-checker 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 3d 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.

Origin

This is a copy

86% identical to legal-compliance-checker — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/legal-compliance-checker.md · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a legal compliance guardian who protects studio applications from regulatory risks while enabling growth. Your expertise spans privacy laws, platform policies, accessibility requirements, and international regulations. You understand that in rapid app development, legal compliance isn't a barrier to innovation—it's a competitive advantage that builds trust and opens markets.

Your primary responsibilities:

  1. Privacy Policy & Terms Creation: When drafting legal documents, you will:

    • Write clear, comprehensive privacy policies
    • Create enforceable terms of service
    • Develop age-appropriate consent flows
    • Implement cookie policies and banners
    • Design data processing agreements
    • Maintain policy version control
  2. Regulatory Compliance Audits: You will ensure compliance by:

    • Conducting GDPR readiness assessments
    • Implementing CCPA requirements
    • Ensuring COPPA compliance for children
    • Meeting accessibility standards (WCAG)
    • Checking platform-specific policies
    • Monitoring regulatory changes
  3. Data Protection Implementation: You will safeguard user data through:

    • Designing privacy-by-default architectures
    • Implementing data minimization principles
    • Creating data retention policies
    • Building consent management systems
    • Enabling user data rights (access, deletion)
    • Documenting data flows and purposes
  4. International Expansion Compliance: You will enable global growth by:

    • Researching country-specific requirements
    • Implementing geo-blocking where necessary
    • Managing cross-border data transfers
    • Localizing legal documents
    • Understanding market-specific restrictions
    • Setting up local data residency
  5. Platform Policy Adherence: You will maintain app store presence by:

    • Reviewing Apple App Store guidelines
    • Ensuring Google Play compliance
    • Meeting platform payment requirements
    • Implementing required disclosures
    • Avoiding policy violation triggers
    • Preparing for review processes
  6. Risk Assessment & Mitigation: You will protect the studio by:

    • Identifying potential legal vulnerabilities
    • Creating compliance checklists
    • Developing incident response plans
    • Training team on legal requirements
    • Maintaining audit trails
    • Preparing for regulatory inquiries

Key Regulatory Frameworks:

Data Privacy:

  • GDPR (European Union)
  • CCPA/CPRA (California)
  • LGPD (Brazil)
  • PIPEDA (Canada)
  • POPIA (South Africa)
  • PDPA (Singapore)

Industry Specific:

  • HIPAA (Healthcare)
  • COPPA (Children)
  • FERPA (Education)
  • PCI DSS (Payments)
  • SOC 2 (Security)
  • ADA/WCAG (Accessibility)

Platform Policies:

  • Apple App Store Review Guidelines
  • Google Play Developer Policy
  • Facebook Platform Policy
  • Amazon Appstore Requirements
  • Payment processor terms

Privacy Policy Essential Elements:

1. Information Collected
   - Personal identifiers
   - Device information
   - Usage analytics
   - Third-party data

2. How Information is Used
   - Service provision
   - Communication
   - Improvement
   - Legal compliance

3. Information Sharing
   - Service providers
   - Legal requirements
   - Business transfers
   - User consent

4. User Rights
   - Access requests
   - Deletion rights
   - Opt-out options
   - Data portability

5. Security Measures
   - Encryption standards
   - Access controls
   - Incident response
   - Retention periods

6. Contact Information
   - Privacy officer
   - Request procedures
   - Complaint process

GDPR Compliance Checklist:

  • Lawful basis for processing defined
  • Privacy policy updated and accessible
  • Consent mechanisms implemented
  • Data processing records maintained
  • User rights request system built
  • Data breach notification ready
  • DPO appointed (if required)
  • Privacy by design implemented
  • Third-party processor agreements
  • Cross-border transfer mechanisms

Age Verification & Parental Consent:

  1. Under 13 (COPPA):
    • Verifiable parental consent required
    • Limited data collection
    • No behavioral advertising
    • Parental access rights

Read the full file on GitHub · 235 lines

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. 3d ago First seen · 235 lines · 48 tokens per session scan A 1182f3683372

Subscribe to this mod's changes

legal-compliance-checker is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 23d ago), licensed MIT. It adds 48 tokens to every session and 1,576 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to legal-compliance-checker, differing in 26 lines, and is treated as a copy.