compliance-testing

compliance-testing is a skill for Claude Code, Codex from summarybotng/summarybot-ng. It costs 43 tokens per session (1,664 once invoked), scanned A, original, MIT.

Regulatory compliance testing for GDPR, CCPA, HIPAA, SOC2, PCI-DSS and industry-specific regulations. Use when ensuring legal compliance, preparing for audits, or handling sensitive data.

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/summarybotng/summarybot-ng/compliance-testing
Any agent
npx skills add summarybotng/summarybot-ng --skill compliance-testing
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/compliance-testing.svg)](https://agentmods.dev/skills/summarybotng/summarybot-ng/compliance-testing)
Your own site
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/compliance-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/compliance-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,664 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00043 $0.01664
Opus 5 $0.00022 $0.00832
Sonnet 5 $0.00009 $0.00333
Haiku 4.5 $0.00004 $0.00166

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

Security

Grade A, and why

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

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.

.claude/skills/compliance-testing/SKILL.md · 233 lines

How it starts

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

Compliance Testing

<default_to_action> When validating regulatory compliance:

  1. IDENTIFY applicable regulations (GDPR, HIPAA, PCI-DSS, etc.)
  2. MAP requirements to testable controls
  3. TEST data rights (access, erasure, portability)
  4. VERIFY encryption and access logging
  5. GENERATE audit-ready reports with evidence

Quick Compliance Checklist:

  • Data subject rights work (access, delete, export)
  • PII is encrypted at rest and in transit
  • Access to sensitive data is logged
  • Consent is tracked with timestamps
  • Payment card data not stored (only tokenized)

Critical Success Factors:

  • Non-compliance = €20M or 4% revenue (GDPR)
  • Audit trail everything
  • Test continuously, not just before audits </default_to_action>

Quick Reference Card

When to Use

  • Legal compliance requirements
  • Before security audits
  • Handling PII/PHI/PCI data
  • Entering new markets (EU, CA, healthcare)

Major Regulations

Regulation Scope Key Focus
GDPR EU data Privacy rights, consent
CCPA California Consumer data rights
HIPAA Healthcare PHI protection
PCI-DSS Payments Card data security
SOC2 SaaS Security controls

Penalties

Regulation Maximum Fine
GDPR €20M or 4% revenue
HIPAA $1.5M per violation
PCI-DSS $100k/month
CCPA $7,500 per violation

GDPR Compliance Testing

// Test data subject rights
test('user can request their data', async () => {
  const response = await api.post('/data-export', { userId });

  expect(response.status).toBe(200);
  expect(response.data.downloadUrl).toBeDefined();

  const data = await downloadFile(response.data.downloadUrl);
  expect(data).toHaveProperty('profile');
  expect(data).toHaveProperty('orders');
});

test('user can delete their account', async () => {
  await api.delete(`/users/${userId}`);

  // All personal data deleted
  expect(await db.users.findOne({ id: userId })).toBeNull();
  expect(await db.orders.find({ userId })).toHaveLength(0);

  // Audit log retained (legal requirement)
  expect(await db.auditLogs.find({ userId })).toBeDefined();
});

test('consent is tracked', async () => {
  await api.post('/consent', {
    userId, type: 'marketing', granted: true,
    timestamp: new Date(), ipAddress: '192.168.1.1'
  });

  const consent = await db.consents.findOne({ userId, type: 'marketing' });
  expect(consent.timestamp).toBeDefined();
  expect(consent.ipAddress).toBeDefined();
});

Read the full file on GitHub · 233 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. today First seen · 233 lines · 43 tokens per session scan A c0fdd0a04490

Subscribe to this mod's changes

compliance-testing is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,664 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-09-03.

Related

Other skills, from other repositories

compliance-audit

Regulatory compliance auditing across GDPR, HIPAA, PCI DSS, SOC 2, and ISO frameworks with automated evidence collection and gap analysis. Use when conducting compliance assessments, preparing for certifications, or implementing regulatory controls.

NickCrew/Claude-Cortex · 48 tokens

privacy-compliance

Comprehensive global privacy compliance agent skill covering GDPR, CCPA/CPRA, HIPAA Privacy Rule, EU AI Act, LGPD, cross-border data transfer mechanisms (SCCs, BCRs, EU-US DPF), PII identification and classification, data minimization, consent management, privacy-by-design patterns, DPIA workflows, data subject access…

JPeetz/agent-skills · 132 tokens

policy-opa

Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA). Use when: (1) Enforcing security and compliance policies across infrastructure and applications, (2) Validating Kubernetes admission control policies, (3) Implementing policy-as-code for compliance frameworks (SOC2, PCI-DSS, GDPR…

AgentSecOps/SecOpsAgentKit · 117 tokens

compliance-review

Compliance & Governance Review: Reviews systems for regulatory compliance — SOC2, HIPAA, PCI-DSS, ISO 27001, LGPD/GDPR. Covers access control, audit logging, encryption, data retention, incident response, and compliance documentation. Use when the user mentions SOC2, HIPAA, PCI, ISO 27001, LGPD, GDPR, compliance…

camilooscargbaptista/cto-toolkit · 103 tokens

privacy-compliance

Use this skill when implementing GDPR or CCPA compliance, designing consent management, conducting DPIAs, or managing data processing agreements. Triggers on GDPR, CCPA, data privacy, consent management, DPIA, data subject rights, privacy policy, cookie consent, and any task requiring privacy regulation compliance or…

ThomasMoreAI/legal-skills-open · 68 tokens

regulatory-compliance-oimiragieo

Validate systems and processes against GDPR/CCPA privacy regulations, privacy-by-design principles, ADA/WCAG accessibility standards, data processing agreements (DPAs), and provide compliance checklists with regulatory change monitoring guidance.

ThomasMoreAI/legal-skills-open · 52 tokens