compliance-design

compliance-design is a skill for Claude Code from joao-aires/agent-skills-public. It costs 43 tokens per session (776 once invoked), scanned A, original, MIT.

A guide for turning legal, contractual, and assurance requirements into system boundaries, controls, owners, and evidence. It separates engineering decisions from legal interpretation and independent assurance.

In plain words
What is it for?
Use it during product or system design and scoped compliance assessments involving data, infrastructure, access, vendors, or customer commitments.
Why use it?
It helps teams determine which obligations apply to a service and connect them to concrete technical and operational work without treating every request as a full audit.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it during product or system design and scoped compliance assessments involving data, infrastructure, access, vendors, or customer commitments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joao-aires/agent-skills-public/compliance-design
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 joao-aires/agent-skills-public --skill compliance-design
Clone the repo
git clone --depth 1 https://github.com/joao-aires/agent-skills-public

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/compliance-design/github.svg)](https://agentmods.dev/skills/joao-aires/agent-skills-public/compliance-design)
Your own site
<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/compliance-design"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/compliance-design/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-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/compliance-design"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/compliance-design.svg" alt="Reviewed on agentmods" width="80" 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 776 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.00043 $0.00776
Opus 5.5 $0.00017 $0.00310
Sonnet 5.5 $0.00009 $0.00155
Haiku 4.5 $0.00004 $0.00078

Measured yesterday against content hash 687c43e24713, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

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.

plugins/governance/skills/compliance-design/SKILL.md · 66 lines

How it starts

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

Connect obligations to system decisions

Establish the intended service, customers/jurisdictions, data processing, delivery model and requested decision. Identify existing commitments, authoritative interpretations and current evidence. Separate a statutory duty, customer contract, voluntary assurance goal and product preference; they have different applicability and decision owners. A small change needs assessment of affected obligations, not an exhaustive organizational audit.

Establish applicability and authority

Investigate relevant facts before asking the user to settle a tradeoff.

  • Record the source, version/date where useful, affected entity/process and why a requirement appears applicable.
  • Consult primary material for substantive interpretation using the source guide.
  • When legal or assurance interpretation remains material, identify the exact unresolved question and qualified decision owner; do not ask the user to guess technical facts or invent an approved interpretation.

Describe the service or processing operation to which the requirement applies. Follow the data and responsibility through people/processes, application and infrastructure, identity, vendors, support, telemetry and recovery. Identify who controls each part and where a supplier or customer must perform an action. A requirement may apply to that whole operation rather than a single code repository.

Use this boundary to decide what the project can demonstrate and what needs evidence from elsewhere. Hosted region, encryption, a provider attestation or a passing scanner can answer a particular question, but each leaves other responsibilities unexamined. Preserve that scope when explaining readiness or gaps.

Derive proportionate controls

For each material applicable obligation or commitment, preserve this reasoning chain:

applicable obligation or commitment
→ intended outcome
→ control, owner and scope
→ implementation and operation
→ evidence and remaining exposure

Read the full file on GitHub · 66 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. yesterday First seen · 66 lines · 43 tokens per session scan A 687c43e24713

Subscribe to this mod's changes

compliance-design is a skill published in the GitHub repository joao-aires/agent-skills-public (2 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 776 once invoked, about $0.0002 per session on Opus 5.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-10-21.

Related

Other skills, from other repositories

fto-triage

Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…

anthropics/claude-for-legal · 81 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens