Implements 42 CFR Part 2 protections for substance use disorder patient records.

Apache-2.0Auto-check passedLegal & Compliance

Install 42 Cfr Part 2

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill 42-cfr-part-2 -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills 42-cfr-part-2 --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/42-cfr-part-2 .claude/skills/42-cfr-part-2 && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
42-cfr-part-2
GitHub stars
301
Token cost
~3.6k tokens
SKILL.md length
1,950 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implements 42 CFR Part 2 protections for substance use disorder patient records.

  • Works in 5 steps: Is conducted by any department or agency… → Is carried out under a license,… → Is supported by funds from any federal… → …
  • Tasks that involve Healthcare and finance regulation
  • SKILL.md covers Overview, Applicability — Who Must Comply, What Records Are Protected —… and Consent Requirements — §2.31, plus 8 more sections
  • Runs Python scripts from its folder

What it does

42 Cfr Part 2 is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).

It sits in Legal & Compliance, covering Healthcare and finance regulation and Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Healthcare and finance regulation
  • Tasks that involve Privacy and GDPR

Example prompts

  • “Use the 42-cfr-part-2 skill to implement 42 CFR Part 2 protections for substance use disorder patient records”
  • “/42-cfr-part-2”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Is conducted by any department or agency of the United States (VA, IHS, military)
  2. Is carried out under a license, certification, registration, or authorization from the federal government (DEA registration for opioid…
  3. Is supported by funds from any federal department or agency (Medicare/Medicaid participation qualifies)
  4. Is assisted by the IRS through tax-exempt status under 26 USC §501(c)(3)
  5. Is conducted by a state or local government receiving federal funds that could be used for SUD programs (even if not directly used for SUD)

What it can do on your machine

Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

42 Cfr Part 2 loads about 3.6k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 1,950 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,950 words, ~3,604 tokens.

Download SKILL.mdSave it as .claude/skills/42-cfr-part-2/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
42-cfr-part-2
description
Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
healthcare-privacy
metadata.tags
42-cfr-part-2, substance-use-disorder, sud-records, re-disclosure, consent, court-order

42 CFR Part 2 — Substance Use Disorder Records

Overview

42 CFR Part 2 establishes federal confidentiality protections for patient records created by federally assisted programs treating substance use disorders (SUDs). Originally enacted under the Comprehensive Alcohol Abuse and Alcoholism Prevention, Treatment, and Rehabilitation Act of 1970 and the Drug Abuse Prevention, Treatment, and Rehabilitation Act of 1972, Part 2 was designed to remove barriers to treatment by ensuring that SUD records could not be used to criminally prosecute or otherwise discriminate against patients. Part 2 is intentionally stricter than HIPAA — it requires specific written consent for most disclosures and prohibits re-disclosure by recipients. The CARES Act §3221 (enacted March 2020) and the subsequent 2024 Final Rule (89 FR 12472, effective February 16, 2024) significantly amended Part 2 to align certain provisions with HIPAA while preserving core patient protections.

Applicability — Who Must Comply

Part 2 Programs

Part 2 applies to any "program" that is federally assisted and holds itself out as providing, and provides, substance use disorder diagnosis, treatment, or referral for treatment. A program is federally assisted if it:

  1. Is conducted by any department or agency of the United States (VA, IHS, military)
  2. Is carried out under a license, certification, registration, or authorization from the federal government (DEA registration for opioid treatment programs)
  3. Is supported by funds from any federal department or agency (Medicare/Medicaid participation qualifies)
  4. Is assisted by the IRS through tax-exempt status under 26 USC §501(c)(3)
  5. Is conducted by a state or local government receiving federal funds that could be used for SUD programs (even if not directly used for SUD)

Asclepius Health Network Applicability: Asclepius operates 3 dedicated SUD treatment facilities and provides SUD treatment services in all 12 hospitals. Because Asclepius participates in Medicare and Medicaid, all SUD treatment records are Part 2 records. Asclepius maintains a separate consent workflow for Part 2 records in its EHR.

General Medical Facilities

A general medical facility (like a hospital ED) is a Part 2 program only with respect to an identified unit that holds itself out as providing SUD diagnosis, treatment, or referral. However, the 2024 amendments clarify that incidental SUD information in a general medical record (e.g., a note that a patient has a history of alcohol use disorder documented during a cardiac admission) is subject to Part 2 only if the information was obtained from a Part 2 program.

What Records Are Protected — §2.12

Part 2 protects records that:

  1. Would identify a patient as having or having had a substance use disorder
  2. Are created by a Part 2 program (or received from a Part 2 program)
  3. Contain SUD diagnosis, treatment, or referral information

The protections apply to any information that would identify an individual as a SUD patient, including the fact that the person is or was a patient in a Part 2 program.

Unlike HIPAA, which permits disclosures for TPO without consent, Part 2 historically required specific written consent for virtually all disclosures. The 2024 amendments introduced a HIPAA-aligned consent-once model for TPO, but with important safeguards.

A valid Part 2 consent must include all of the following:

ElementRequirement
Name of patientFull legal name of the patient
Name of Part 2 programSpecific program making the disclosure
Recipient nameName or general designation of the person(s) or entity to whom disclosure is made
PurposeThe purpose of the disclosure must be specified
Information to be disclosedHow much and what kind of information is to be disclosed
Patient signaturePatient (or authorized representative) signature
Date signedDate the consent was signed
Revocability statementStatement that consent is subject to revocation at any time, except to the extent the program has already acted in reliance on it
ExpirationDate, event, or condition upon which consent will expire (if none, the consent must state it expires when the purpose is fulfilled)
Re-disclosure prohibition noticeStatement that information disclosed pursuant to consent may not be further disclosed unless permitted by Part 2

The 2024 Final Rule (89 FR 12472) introduced §2.33, allowing a single prior written consent for all future uses and disclosures for treatment, payment, and healthcare operations:

Key Features of §2.33 Consent:

  • Patient may provide a single written consent covering all future TPO disclosures
  • Consent covers disclosures to treating providers, payers, and entities performing healthcare operations
  • Consent need not name each specific recipient — a general designation of recipient categories is sufficient (e.g., "my treating providers" or "my health plan")
  • Consent does not expire unless the patient revokes it
  • Patient retains the right to revoke at any time (revocation effective prospectively)
  • Recipients remain bound by Part 2's anti-discrimination and limited use/disclosure restrictions

Asclepius Health Network Implementation: Asclepius offers patients a §2.33 TPO consent form at SUD program intake. Patients who sign the TPO consent have their Part 2 records flagged in the EHR for permitted sharing with treating providers and the patient's health plan. Patients who decline the TPO consent retain the traditional per-disclosure consent process. All consent decisions are documented in the EHR.

Re-Disclosure Prohibition — §2.32

The Core Part 2 Protection

Each disclosure of Part 2 records must be accompanied by the following notice:

"This record which has been disclosed to you is protected by federal confidentiality rules (42 CFR Part 2). The federal rules prohibit you from making any further disclosure of information in this record that identifies a patient as having or having had a substance use disorder either directly, by reference to publicly available information, or through verification of such identification by another person unless further disclosure is expressly permitted by the written consent of the individual whose information is being disclosed or as otherwise permitted by 42 CFR Part 2. A general authorization for the release of medical or other information is NOT sufficient for this purpose (see §2.31). The federal rules restrict any use of the information to investigate or prosecute with regard to a crime any patient with a substance use disorder, except as provided at §§2.12(c)(5) and 2.65."

2024 Amendment Impact on Re-Disclosure

Under the 2024 amendments, when Part 2 records are disclosed pursuant to a §2.33 TPO consent:

  • Recipients who are HIPAA covered entities or business associates may further use and disclose the records under HIPAA rules (effectively treating them as HIPAA-protected PHI for TPO purposes)
  • The re-disclosure prohibition is relaxed for HIPAA-covered recipients to permit standard HIPAA-authorized TPO activities
  • However, Part 2's prohibition on use in civil, criminal, administrative, or legislative proceedings against the patient is preserved (§2.12(d))
  • Non-HIPAA-covered recipients remain bound by the traditional re-disclosure prohibition

Court Order Requirements — §2.64, §2.65

Authorizing Disclosures by Court Order

When consent is unavailable or not applicable, a court may issue an order authorizing disclosure only after the court finds "good cause" — meaning that:

  1. Other ways of obtaining the information are not available or would not be effective
  2. The public interest and need for disclosure outweigh the potential injury to the patient, the physician-patient relationship, and the treatment services
Show full SKILL.md (769 more words)Show less
Application Process

An application for a court order must use a fictitious name for the patient and may not disclose patient-identifying information to the court unless the patient is the applicant. The application must be filed under seal.

Criminal Investigations — §2.65

Part 2 records may not be used to investigate or prosecute a patient with respect to a substance use disorder-related crime, with very limited exceptions:

  • A court order under §2.65 requires an additional finding that the crime is extremely serious (causing or threatening to cause death or serious bodily injury)
  • The order must limit disclosure to the information essential to fulfill the purpose and limit access to those who need the information

Qualified Service Organization Agreements — §2.11(a)

Part 2 uses QSOAs (analogous to HIPAA BAAs) for entities that provide services to Part 2 programs:

QSOA RequirementDescription
Written agreementMust be in writing, signed by both parties
Acknowledge Part 2 obligationsQSO acknowledges it is bound by Part 2
Permitted activitiesData processing, laboratory analyses, legal/medical/accounting/other professional services
No re-disclosureQSO agrees not to re-disclose except as permitted by Part 2
Resistibility to compulsory processQSO agrees to resist judicial process seeking patient records unless permitted by Part 2

2024 Amendment: Existing QSOAs may be maintained, but programs may now transition to using HIPAA-style BAAs for Part 2 records, provided the BAA includes Part 2's specific protections (anti-discrimination, use restriction for investigations/prosecutions).

Comparison: Part 2 vs HIPAA (Post-2024 Amendments)

AspectHIPAA42 CFR Part 2 (Post-2024)
Consent for TPONot requiredWritten consent required (§2.33 single consent available)
Consent specificityN/A (no consent needed for TPO)Must include specified elements; may use general recipient designation for TPO
Re-disclosureHIPAA allows under permitted uses/disclosuresRestricted — recipients who are HIPAA CEs may use under HIPAA for TPO; anti-discrimination protections preserved
Use in legal proceedings against patientNo prohibitionProhibited except under specific court order (§2.12(d))
Breach notificationRequired under §164.400-414Now aligned with HIPAA breach notification requirements (2024 amendment)
PenaltiesHIPAA civil and criminal penaltiesPart 2 criminal penalties (§2.4) PLUS HIPAA penalties for covered entities (2024 amendment)
EnforcementOCRSAMHSA (Part 2-specific) AND OCR (aligned enforcement, 2024 amendment)
Patient right of accessYes, §164.524Now aligned with HIPAA (2024 amendment)

Special Populations and Situations

Minors — §2.14
  • State law governs whether a minor may consent to SUD treatment
  • If the minor can lawfully consent to SUD treatment, the minor controls the Part 2 consent for disclosure
  • A parent/guardian may consent for a minor who cannot lawfully consent to treatment, but the Part 2 program may deny parental access to protect the minor
Medical Emergencies — §2.51

Disclosure without consent is permitted in a bona fide medical emergency to medical personnel to the extent necessary to meet the emergency. The program must document: the name and affiliation of the recipient, the name of the individual authorizing disclosure, the date and time of disclosure, the nature of the emergency, and the information disclosed.

Audit and Evaluation — §2.53

Federal, state, and local government agencies and third-party payers may access Part 2 records for audit and evaluation purposes without consent, subject to restrictions on re-disclosure and a prohibition on use in criminal investigation or prosecution.

Asclepius Health Network Part 2 Compliance Program

  1. EHR Segmentation: Part 2 records are flagged with a sensitivity code; access controls prevent viewing by users without Part 2 authorization
  2. Consent Management: Dedicated consent forms tracked in the EHR with consent status (granted/revoked/never requested) visible to clinical staff
  3. Staff Training: Annual Part 2-specific training for all clinical, billing, and HIM staff; quarterly refresher for SUD program staff
  4. HIE Participation: Part 2 records are excluded from automated HIE feeds unless patient has signed §2.33 TPO consent
  5. Breach Response: Part 2 breach response follows HIPAA breach notification procedures (aligned under 2024 amendments) with additional SAMHSA reporting

Enforcement

Criminal Penalties — §2.4

Any person who violates Part 2 is subject to:

  • First offense: Fine of not more than $500
  • Subsequent offenses: Fine of not more than $5,000
2024 Amendment Penalty Alignment

The 2024 Final Rule aligned Part 2 enforcement with HIPAA's penalty tiers for covered entities and business associates, enabling OCR to impose HIPAA-level civil monetary penalties for Part 2 violations.

Integration Points

  • hipaa-privacy-rule: Part 2 records held by HIPAA CEs are subject to both Part 2 and HIPAA; Part 2 is the more restrictive standard
  • hipaa-breach-notify: Part 2 breach notification now aligned with HIPAA breach notification requirements
  • hipaa-minimum-necessary: Part 2 consent specifies the scope of disclosure; minimum necessary applies separately under HIPAA
  • hipaa-baa-management: QSOAs serve Part 2's function analogous to BAAs; 2024 amendments permit BAA use with Part 2 additions

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/42-cfr-part-2 of mukul975/Privacy-Data-Protection-Skills.

  • SKILL.md
  • assets/template.md
  • references/standards.md
  • references/workflows.md
  • scripts/process.py

Open the folder on GitHubat commit 9b2ef9e

Compare with similar skills

42 Cfr Part 2 next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

42 Cfr Part 2 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
42 Cfr Part 2 this skillmukul975/Privacy-Data-Protection-Skills301—~3.6kAutomated safety check: PassApache-2.0
HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed5.5k—~1.7kAutomated safety check: PassApache-2.0
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT
Audit Reportharness/harness-skills115—~1.3kAutomated safety check: PassApache-2.0
Anne WojcickiK-Dense-AI/mimeographs129—~1.5kAutomated safety check: PassMIT
Dpa Checklist ReviewLegalQuants/lq-ai150—~3.7kAutomated safety check: PassApache-2.0

Similar skills

  • Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated today
    Legal & ComplianceAuto-check passed
  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed
  • Audit Report

    harness/harness-skills

    Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.

    115 GitHub stars~1.3k tokensUpdated 4 days ago
    Legal & ComplianceAuto-check passed
  • Anne Wojcicki

    K-Dense-AI/mimeographs

    Applies the strategic frameworks and mental models of Anne Wojcicki, co-founder and CEO of 23andMe.

    129 GitHub stars~1.5k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Dpa Checklist Review

    LegalQuants/lq-ai

    A skill your agent uses when the user provides a Data Processing Agreement, Data Processing Addendum, or HIPAA Business Associate Agreement and asks whether it contains the terms required under the…

    150 GitHub stars~3.7k tokensUpdated today
    Legal & ComplianceAuto-check passed
  • Auditing Deidentification Runs

    maziyarpanahi/openmed

    Produce a signed, reproducible, no-PHI audit trail for an OpenMed de-identification run via deidentify(audit=True).

    5.5k GitHub stars~1.8k tokensUpdated today
    Legal & ComplianceAuto-check passed

More from mukul975/Privacy-Data-Protection-Skills

All 280 skills in this repo
  • Age Gating Services

    mukul975/Privacy-Data-Protection-Skills

    Implements age-gating mechanisms for online services to restrict access based on user age.

    301 GitHub stars~3.7k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Data Retention

    mukul975/Privacy-Data-Protection-Skills

    Manages AI model retention and machine unlearning requirements.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Dpia

    mukul975/Privacy-Data-Protection-Skills

    Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.

    301 GitHub stars~3.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Dpia Mitigation Plan

    mukul975/Privacy-Data-Protection-Skills

    Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).

    301 GitHub stars~846 tokensUpdated 6 mo ago
    Auto-check passed
  • Gdpr Accountability

    mukul975/Privacy-Data-Protection-Skills

    Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Pia Threshold Screening

    mukul975/Privacy-Data-Protection-Skills

    Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.

    301 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed

Questions about 42 Cfr Part 2

What does 42 Cfr Part 2 do?

Implements 42 CFR Part 2 protections for substance use disorder patient records. 42 Cfr Part 2 is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements 42 CFR Part 2 protections for substance use disorder patient records.

When should I use 42 Cfr Part 2?

42 Cfr Part 2 fits situations like: tasks that involve Healthcare and finance regulation; tasks that involve Privacy and GDPR.

How do I install 42 Cfr Part 2 in Claude Code?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill 42-cfr-part-2 -a claude-code`. Or copy the skill folder (skills/privacy/42-cfr-part-2 in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/42-cfr-part-2 in your project. Claude Code loads it when a task matches its description.

How do I install 42 Cfr Part 2 in Codex?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill 42-cfr-part-2 -a codex`. Or copy the skill folder (skills/privacy/42-cfr-part-2 in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/42-cfr-part-2 in your project. Codex loads it when a task matches its description.

Can I use 42 Cfr Part 2 in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill 42-cfr-part-2 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/42-cfr-part-2, .gemini/skills/42-cfr-part-2, .github/skills/42-cfr-part-2 and .opencode/skills/42-cfr-part-2 in your project.

What does 42 Cfr Part 2 need to run?

Going by SKILL.md and its folder, 42 Cfr Part 2 needs Python for the scripts in its folder. Our summary lists: Python 3.

Does 42 Cfr Part 2 access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 42 Cfr Part 2 safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does 42 Cfr Part 2 use?

42 Cfr Part 2 is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 42 Cfr Part 2 use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to 42 Cfr Part 2?

Skills that share tags, products or a category with 42 Cfr Part 2: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Audit Report (harness/harness-skills, 115 stars) and Anne Wojcicki (K-Dense-AI/mimeographs, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 42 Cfr Part 2?

mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.

Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.