Compliance Patterns Specification

Compliance Patterns Specification is a skill for Claude Code, Codex from JanoshMoshiri/MarkdownLLM. It costs 16 tokens per session (1,583 once invoked), scanned A, original, MIT.

A reference library of examples showing how to encode compliance as verifiable reasoning. Compliance means meeting rules such as privacy, access logging, data location, and retention requirements.

In plain words
What is it for?
It is for designing regulated domains, teaching agents compliance patterns, and comparing compliant behavior with documented violations.
Why use it?
It helps developers represent compliance with concrete positive and negative examples instead of relying only on abstract rules or checklists. This makes decisions easier to evaluate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for designing regulated domains, teaching agents compliance patterns, and comparing compliant behavior with documented violations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/janoshmoshiri/markdownllm/compliance-patterns-specification
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.

Any agent
npx skills add JanoshMoshiri/MarkdownLLM --skill compliance-patterns-specification
Clone the repo
git clone --depth 1 https://github.com/JanoshMoshiri/MarkdownLLM

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 Patterns Specification

README.md
[![agentmods](https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/compliance-patterns-specification/github.svg)](https://agentmods.dev/skills/janoshmoshiri/markdownllm/compliance-patterns-specification)
Your own site
<a href="https://agentmods.dev/skills/janoshmoshiri/markdownllm/compliance-patterns-specification"><img src="https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/compliance-patterns-specification/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Compliance Patterns Specification

Your own site · 80×15
<a href="https://agentmods.dev/skills/janoshmoshiri/markdownllm/compliance-patterns-specification"><img src="https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/compliance-patterns-specification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,583 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 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.1 $0.00016 $0.01583
Opus 5 $0.00008 $0.00792
Sonnet 5 $0.00003 $0.00317
Haiku 4.5 $0.00002 $0.00158

Measured 9d ago against content hash df8857f668a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

Compliance Patterns Specification 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 9d 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.

examples/compliance-patterns/skills/compliance-patterns-specification.skill.md · 193 lines

How it starts

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

Compliance Patterns Specification

What This Domain Is

A collection of example things demonstrating compliance patterns, multi-lens reasoning, and regulatory best practices for domains operating under constraints (GDPR, HIPAA, financial regulations, etc.).

This is not a compliance domain itself. It's a reference library for domain builders creating regulated systems.

Philosophy: Why Examples Work for Compliance

Traditional compliance approaches:

  • Write rules and hope the system follows them
  • Rely on checklists to prevent violations
  • Separate "compliance team" from "engineering team"
  • End up with technical debt and audit friction

Better approach: Make compliance verifiable through examples.

LLMs excel at verifiable reasoning—tasks with clear right/wrong answers. Compliance is inherently verifiable:

  • ✓ Data classified or not classified
  • ✓ Access logged or not logged
  • ✓ Data residency UK or non-UK
  • ✓ Retention policy followed or violated

By providing both positive examples (compliant patterns) and negative examples (violations with explanations), we transform compliance from abstract rules into verifiable patterns. The LLM learns not just "what to do" but "why this is right and that is wrong."

Contrast Creates Clarity

Showing both the correct pattern AND the violation pattern (with consequences) gives the LLM two concrete reference points. This is why anti-patterns paired with remediation are more effective than rules alone—the LLM can verify its reasoning against both.

Core Principles

Verifiable Compliance: Every compliance decision should be reducible to verifiable facts, not subjective interpretation.

Multi-Lens Reasoning: Every significant decision should be evaluated through domain logic, compliance logic, and audit logic.

Explicit Conflicts: When lenses conflict, surface the conflict for human resolution rather than hiding it in logic.

Pattern-Based Learning: LLMs learn from examples; compliance becomes reinforced through every decision, not imposed as external constraints.

Read the full file on GitHub · 193 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. 9d ago First seen · 193 lines · 16 tokens per session scan A df8857f668a6

Subscribe to this mod's changes

Compliance Patterns Specification is a skill published in the GitHub repository JanoshMoshiri/MarkdownLLM (5 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 1,583 once invoked, about $0.0001 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-04.

Related

Other skills, from other repositories

policy-qa

Triage loop for inbound HR policy questions. Classifies each new question from the HR inbox as answerable from the documented Notion policy library or as needing HR's judgment, drafts a grounded Gmail reply for the former, and escalates the latter — anything ambiguous, legal, personal, or compensation-related — to…

kortix-ai/suna · 77 tokens

patsnap-ip-innovation-courses

Patsnap IP & Innovation Courses MCP for AI agents. A one-stop learning entry for courses, course details, and training materials on IP and innovation. It helps teams build a structured understanding of patents, search, analysis, and business use while lowering the learning barrier for new users. It is useful for…

patsnap/mcp · 81 tokens

learn-law-with-rohas

Acts as an interactive legal tutor for learning a law, legal subject, doctrine, judgment, procedure, or legal concept. Builds a learning path around the user's topic and level, teaches concepts step by step, uses examples and hypotheticals, asks questions and quizzes, explains mistakes, adapts difficulty, revises weak…

rohasnagpal/legal-ai-skills · 150 tokens

legal-explainer

Explains laws, legal concepts, judgments, clauses, rights, obligations, procedures, and legal positions in clear plain language without losing legal accuracy. Use when a user asks "what does this mean?", "explain this law simply", "explain this clause", "what does this judgment actually say", "explain this to a…

rohasnagpal/legal-ai-skills · 127 tokens

grad-public-choice

Apply public choice theory to analyze political decision-making as rational self-interested behavior. Use this skill when the user needs to evaluate government policy failures, rent-seeking costs, voting outcomes, or bureaucratic incentives, especially when the assumption of benevolent government is questionable.

asgard-ai-platform/skills · 57 tokens

creative-commons-explainer

Explains a specific Creative Commons licence in plain language, telling a media professional exactly what they can and cannot do with the licensed content — including attribution requirements, commercial use rules, and derivative work restrictions.

ur-grue/autopunk-media-skills · 47 tokens