compliance

A framework and checklist for meeting legal requirements such as GDPR, the European Union privacy law, CCPA, employment law, and industry regulations.

In plain words
What is it for?
Use it to assess privacy practices, prepare compliance policies, handle requests to access or delete personal data, and run compliance audits.
Why use it?
It turns broad compliance duties into checks for legal bases, user rights, policies, records, and data-protection measures.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/saolalab/clawforce/compliance
Any agent
npx skills add saolalab/clawforce --skill compliance
Clone the repo
git clone --depth 1 https://github.com/saolalab/clawforce

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,287 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00035 $0.02287
Opus 5 $0.00017 $0.01144
Sonnet 5 $0.00007 $0.00457
Haiku 4.5 $0.00003 $0.00229

Measured 3d ago against content hash bc641516e71d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

compliance 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.

marketplace/roles/legal-counsel/workspace/skills/compliance/SKILL.md · 338 lines

How it starts

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

Compliance

This skill provides frameworks and checklists for regulatory compliance across multiple jurisdictions and regulations.

GDPR Compliance Checklist

The General Data Protection Regulation (GDPR) applies to companies processing personal data of EU residents.

Legal Basis

  • Identified legal basis for each data processing activity (consent, contract, legal obligation, vital interests, public task, legitimate interests)
  • Documented legal basis for each processing activity
  • Consent mechanisms meet GDPR standards (freely given, specific, informed, unambiguous)

Data Subject Rights

  • Right to access — Process for handling data subject access requests (30-day response time)
  • Right to rectification — Process for correcting inaccurate data
  • Right to erasure ("right to be forgotten") — Process for deleting data upon request
  • Right to restrict processing — Process for limiting how data is used
  • Right to data portability — Process for providing data in machine-readable format
  • Right to object — Process for handling objections to processing
  • Automated decision-making — Procedures for handling automated decisions and profiling

Data Protection Measures

  • Data Protection Impact Assessment (DPIA) conducted for high-risk processing
  • Privacy by Design and Privacy by Default implemented
  • Data minimization — Only collect necessary data
  • Purpose limitation — Use data only for stated purposes
  • Storage limitation — Delete data when no longer needed
  • Encryption of personal data in transit and at rest
  • Access controls and authentication mechanisms
  • Regular security assessments and audits

Documentation

  • Records of processing activities maintained
  • Privacy policy updated and GDPR-compliant
  • Data processing agreements (DPAs) with all processors
  • Breach notification procedures documented (72-hour notification requirement)
  • Data Protection Officer (DPO) appointed if required

Read the full file on GitHub · 338 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 · 338 lines · 35 tokens per session scan A bc641516e71d

Subscribe to this mod's changes

compliance is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 2,287 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-30.