compliance-checker

A code review guide for checking software against security standards and privacy laws, including OWASP, GDPR, HIPAA, and PCI-DSS.

In plain words
What is it for?
Use it to review input handling, encryption, access control, session management, sensitive data protection, and other compliance requirements, then produce a gap report.
Why use it?
It helps reveal missing security controls and gaps against a required standard before they become audit findings or security problems.

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/curiouslearner/devkit/compliance-checker
Any agent
npx skills add CuriousLearner/devkit --skill compliance-checker
Clone the repo
git clone --depth 1 https://github.com/CuriousLearner/devkit

Made for: Claude Code, Codex.

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 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.00015 $0.06611
Opus 5 $0.00008 $0.03306
Sonnet 5 $0.00003 $0.01322
Haiku 4.5 $0.00002 $0.00661

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

Security

Grade A, and why

compliance-checker scanned grade A with 2 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(url); // Can access internal services

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const { execFile } = require('child_process');
skills/compliance-checker/SKILL.md · 1,033 lines

How it starts

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

Compliance Checker Skill

Check code against security compliance standards and best practices.

Instructions

You are a security compliance expert. When invoked:

  1. Security Standards Compliance:

    • OWASP Top 10
    • OWASP ASVS (Application Security Verification Standard)
    • CWE Top 25 Most Dangerous Software Weaknesses
    • SANS Top 25
    • NIST Cybersecurity Framework
    • ISO 27001 controls
  2. Industry-Specific Compliance:

    • PCI-DSS (Payment Card Industry)
    • HIPAA (Healthcare)
    • GDPR (Data Privacy - EU)
    • SOC 2 (Service Organization Controls)
    • CCPA (California Consumer Privacy Act)
    • FERPA (Education)
  3. Coding Standards:

    • Secure coding guidelines
    • Input validation requirements
    • Output encoding standards
    • Cryptography standards
    • Session management requirements
    • Error handling best practices
  4. Data Protection:

    • Encryption at rest
    • Encryption in transit
    • Data classification
    • Sensitive data handling
    • Data retention policies
    • Personally Identifiable Information (PII) protection
  5. Generate Report: Comprehensive compliance assessment with gap analysis

OWASP Top 10 (2021)

A01:2021 - Broken Access Control

Checklist
- [ ] Authorization checks on all protected resources
- [ ] No access control bypass via URL manipulation
- [ ] Proper CORS configuration
- [ ] No insecure direct object references (IDOR)
- [ ] Metadata manipulation prevention
- [ ] JWT tokens validated properly
- [ ] Force browsing protection
- [ ] API access controls enforced
Detection Patterns
// ❌ VIOLATION - No authorization check
app.get('/api/users/:id', authenticateUser, async (req, res) => {
  const user = await User.findById(req.params.id);
  res.json(user);  // Any authenticated user can access any user data
});

// ✅ COMPLIANT - Proper authorization
app.get('/api/users/:id', authenticateUser, async (req, res) => {
  if (req.params.id !== req.user.id && !req.user.isAdmin) {
    return res.status(403).json({ error: 'Forbidden' });
  }
  const user = await User.findById(req.params.id);
  res.json(user);
});

Read the full file on GitHub · 1,033 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. 2d ago First seen · 1,033 lines · 15 tokens per session scan A 71985fa13956

Subscribe to this mod's changes

compliance-checker is a skill published in the GitHub repository CuriousLearner/devkit (27 stars, last pushed 10mo ago), licensed MIT. It adds 15 tokens to every session and 6,611 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens