design-compliance-architecture

design-compliance-architecture is a skill for Claude Code from pjt222/agent-almanac. It costs 100 tokens per session (3,117 once invoked), scanned A, original, MIT.

A framework for mapping regulations to computer systems in a regulated organisation. It inventories systems, classifies their importance, assigns GAMP 5 categories, and defines how compliance is governed.

In plain words
What is it for?
Use it to create a compliance framework for a regulated site, department, or programme. It supports system inventories, regulatory traceability, validation planning, and quality documentation.
Why use it?
It helps teams understand which rules apply to which systems and avoid gaps in classification, validation, or oversight. It also provides a common structure after organisational changes or audit findings.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the agent-almanac plugin — 122 skills, 76 agents shipped together

Good fit Use it to create a compliance framework for a regulated site, department, or programme. It supports system inventories, regulatory traceability, validation planning, and quality documentation.

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

Made for: Claude Code.

Or install agent-almanac, the plugin that ships this one along with the rest of its 122 skills, 76 agents.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/design-compliance-architecture"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/design-compliance-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,117 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00100 $0.03117
Opus 5 $0.00050 $0.01558
Sonnet 5 $0.00020 $0.00623
Haiku 4.5 $0.00010 $0.00312

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

Security

Grade A, and why

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

i18n/caveman-lite/skills/design-compliance-architecture/SKILL.md · 276 lines

How it starts

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

Design Compliance Architecture

Establish the top-level compliance framework that maps regulations to systems, classifies criticality, and defines governance for a regulated environment.

When to Use

  • A new regulated facility, department, or programme is being established
  • An existing organisation needs to formalise its compliance posture across multiple systems
  • A regulatory gap analysis reveals missing system classification or validation strategy
  • Mergers, acquisitions, or reorganisations require harmonising compliance across entities
  • Preparing a site master file or quality manual that references computerized systems

Inputs

  • Required: List of computerized systems in scope (name, purpose, vendor/custom)
  • Required: Applicable regulatory frameworks (21 CFR Part 11, EU Annex 11, GMP, GLP, GCP, ICH Q7, ICH Q10)
  • Required: Organisational context (department, site, product types)
  • Optional: Existing validation master plan or quality manual
  • Optional: Previous audit findings or regulatory inspection observations
  • Optional: Organisational chart with quality and IT reporting lines

Procedure

Step 1: Build the System Inventory

Create a comprehensive inventory of all computerized systems:

# System Inventory
## Document ID: SI-[SITE]-[YYYY]-[NNN]

| ID | System Name | Version | Vendor | Purpose | Department | Data Types | Users |
|----|-------------|---------|--------|---------|------------|------------|-------|
| SYS-001 | LabWare LIMS | 8.1 | LabWare Inc. | Sample management and testing | QC | Test results, COA | 45 |
| SYS-002 | SAP ERP | S/4HANA | SAP SE | Batch release and inventory | Production | Batch records, BOM | 120 |
| SYS-003 | Custom R/Shiny | 2.1.0 | Internal | Statistical analysis | Biostatistics | Clinical data | 8 |
| SYS-004 | Windows Server | 2022 | Microsoft | File server | IT | Documents | 200 |

Got: Every system that creates, modifies, stores, retrieves, or transmits GxP-relevant data is listed. If fail: If system owners cannot provide complete information, document the gap and schedule a discovery workshop. Missing systems are a critical compliance risk.

Read the full file on GitHub · 276 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 · 276 lines · 100 tokens per session scan A 39c655086e8f

Subscribe to this mod's changes

design-compliance-architecture is a skill published in the GitHub repository pjt222/agent-almanac (33 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 3,117 once invoked, about $0.0005 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.