HIPAA Pre-Deployment Compliance Check
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators.
$ npx skills add cbrock84/headcount --skill regulatory-compliance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount regulatory-compliance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/legal-risk/skills/regulatory-compliance .claude/skills/regulatory-compliance && rm -rf skills-srcUse ~/.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/
Install the "regulatory-compliance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-compliance into .claude/skills/regulatory-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-compliance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-complianceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill regulatory-compliance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount regulatory-compliance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/legal-risk/skills/regulatory-compliance .agents/skills/regulatory-compliance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "regulatory-compliance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-compliance into .agents/skills/regulatory-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-compliance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill regulatory-compliance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount regulatory-compliance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/legal-risk/skills/regulatory-compliance .cursor/skills/regulatory-compliance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "regulatory-compliance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-compliance into .cursor/skills/regulatory-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-compliance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/legal-risk/skills/regulatory-compliance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill regulatory-compliance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount regulatory-compliance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/legal-risk/skills/regulatory-compliance .gemini/skills/regulatory-compliance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "regulatory-compliance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-compliance into .gemini/skills/regulatory-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-compliance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount regulatory-complianceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill regulatory-compliance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/legal-risk/skills/regulatory-compliance .github/skills/regulatory-compliance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "regulatory-compliance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-compliance into .github/skills/regulatory-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-compliance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill regulatory-compliance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount regulatory-compliance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/legal-risk/skills/regulatory-compliance .opencode/skills/regulatory-compliance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "regulatory-compliance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/regulatory-compliance into .opencode/skills/regulatory-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-compliance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
regulatory-complianceIdentifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators.
Regulatory Compliance is an agent skill from cbrock84/headcount. Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Legal & Compliance, covering Regulatory compliance. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Regulatory Compliance loads about 1.1k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 610 words of instructions outside code blocks.
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.
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); files beside SKILL.md are not scanned.
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 610 words, ~1,120 tokens.
.claude/skills/regulatory-compliance/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Compliance failures are rarely defiance. They are almost always an obligation nobody knew applied, in a jurisdiction nobody was watching, discovered by someone external.
This structures the work and names what to ask. Which regulations apply, and what they require, are legal determinations that vary by jurisdiction and change — they belong with qualified counsel. Nothing here substitutes for that.
The first question is not "are we SOC 2 compliant" but "what are we actually obliged to do, by whom, and what happens if we do not." Build the map from facts about the business:
legal-risk:privacy-and-data-protection.Distinguish three things that get conflated: law you must follow, certifications you choose to obtain commercially, and contractual commitments you signed. Only the first carries state enforcement; all three carry consequences.
SOC 2, ISO 27001 and their equivalents demonstrate that controls exist and operate. They do not establish that you meet any legal obligation, and a clean report is not a defense to a regulator.
Where they earn their cost is commercially — an enterprise prospect makes the certification a condition of the deal, and the certification is what unblocks it. Scope them to what the market asks for rather than to everything, since scope drives cost more than any other decision.
A compliance program that produces policies and stops is a shelf. What makes it real:
finance:internal-controls-and-audit for the control design pattern.Respond promptly, accurately, and narrowly — answer what was asked. Route everything through counsel before it goes out, preserve records from the moment you are aware, and never let an informal conversation become an undocumented commitment.
Findings get root-caused like any other failure. A remediation that consists of retraining people on a process that made the failure easy will produce the same finding next cycle.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Compliance automation — Vanta, Drata, Secureframe, Keel GRC, and similar — collects evidence continuously and maps one control across several frameworks. It earns its cost on the second audit far more often than the first.
Policy and attestation lives in those same tools, or in the HRIS, or in Confluence. What matters is that a policy carries a version, an owner, and a record of who acknowledged it.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in plugins/legal-risk/skills/regulatory-compliance of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Regulatory Compliance 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Regulatory Compliance this skillcbrock84/headcount | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.6k | Automated safety check: Notes | MIT | |
| Iso42001Sushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Legal Compliance SearchSerein-81/financial_rag | 148 | — | ~1.6k | Automated safety check: Notes | None |
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
K-Dense-AI/scientific-agent-skills
Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert ISO 42001 AI Management System (AIMS) compliance advisor.
Serein-81/financial_rag
Looks up current company registration rules, industry licences and compliance obligations in China through live web search, tailored to the business profile.
zh-xx/legal-assistant-skills
广告合规审核技能,用于审核广告素材是否符合中国广告法及相关法规。适用场景:(1) 用户提交广告文案、广告素材要求合规审核时;(2) 用户提到"广告审核""广告合规""广告法审查"等关键词时;(3) 用户要求检查广告内容是否存在违法违规风险时;(4) 用户提交房地产、食品、医疗、药品、互联网等行业广告要求专项审核时。审核依据涵盖《广告法》《反不正当竞争法》及行业专项法规。
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Categories
Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Regulatory Compliance is an agent skill from cbrock84/headcount. Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators.
Regulatory Compliance fits situations like: tasks that involve Regulatory compliance.
Run `npx skills add cbrock84/headcount --skill regulatory-compliance -a claude-code`. Or copy the skill folder (plugins/legal-risk/skills/regulatory-compliance in cbrock84/headcount) into .claude/skills/regulatory-compliance in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cbrock84/headcount --skill regulatory-compliance -a codex`. Or copy the skill folder (plugins/legal-risk/skills/regulatory-compliance in cbrock84/headcount) into .agents/skills/regulatory-compliance in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill regulatory-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regulatory-compliance, .gemini/skills/regulatory-compliance, .github/skills/regulatory-compliance and .opencode/skills/regulatory-compliance in your project.
SKILL.md names no scripts, command-line tools or credentials: Regulatory Compliance is instructions for the agent only.
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.
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. Review the folder before installing.
Regulatory Compliance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.5k 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 1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Regulatory Compliance: HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars) and Iso42001 (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.