HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring.
Install Hipaa Mobile Health
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-mobile-health --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/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/hipaa-mobile-health .claude/skills/hipaa-mobile-health && 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 "hipaa-mobile-health" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-health into .claude/skills/hipaa-mobile-health/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-mobile-health", 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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-healthType 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-mobile-health --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/hipaa-mobile-health .agents/skills/hipaa-mobile-health && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hipaa-mobile-health" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-health into .agents/skills/hipaa-mobile-health/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-mobile-health", 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-mobile-health --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/hipaa-mobile-health .cursor/skills/hipaa-mobile-health && 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 "hipaa-mobile-health" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-health into .cursor/skills/hipaa-mobile-health/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-mobile-health", 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/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/hipaa-mobile-health--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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-mobile-health --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/hipaa-mobile-health .gemini/skills/hipaa-mobile-health && 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 "hipaa-mobile-health" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-health into .gemini/skills/hipaa-mobile-health/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-mobile-health", 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 mukul975/Privacy-Data-Protection-Skills hipaa-mobile-healthInstalls 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/hipaa-mobile-health .github/skills/hipaa-mobile-health && 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 "hipaa-mobile-health" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-health into .github/skills/hipaa-mobile-health/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-mobile-health", 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-mobile-health --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/hipaa-mobile-health .opencode/skills/hipaa-mobile-health && 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 "hipaa-mobile-health" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-mobile-health into .opencode/skills/hipaa-mobile-health/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-mobile-health", 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.
Facts
- Skill name
hipaa-mobile-health- GitHub stars
- 301
- Token cost
- ~1.9k tokens
- SKILL.md length
- 833 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring.
- Works in 3 steps: Mobile devices used to access, receive,… → Lost or stolen unencrypted mobile… → The use of personal mobile devices…
- Tasks that involve Healthcare and finance regulation
- SKILL.md covers Overview, Regulatory Framework, Mobile Device Security… and BYOD Policy Requirements, plus 3 more sections
- Runs Python scripts from its folder
What it does
Hipaa Mobile Health is an agent skill from mukul975/Privacy-Data-Protection-Skills. Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring. Covers OCR guidance on mobile device PHI, FDA-regulated mobile medical applications, FTC Health Breach Notification Rule for non-HIPAA apps, BYOD policies, and encryption requirements for ePHI on mobile platforms. Keywords: mHealth, mobile health, HIPAA mobile, wearable, remote monitoring, BYOD, mobile device management, app privacy.
Its SKILL.md is about 1.9k 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. 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
Example prompts
- “Use the hipaa-mobile-health skill to address HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient…”
- “/hipaa-mobile-health”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Mobile devices used to access, receive, transmit, or store ePHI must comply with Security Rule safeguards
- Lost or stolen unencrypted mobile devices containing ePHI constitute presumed breaches under the Breach Notification Rule
- The use of personal mobile devices (BYOD) does not exempt the entity from HIPAA compliance
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
Hipaa Mobile Health loads about 1.9k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 833 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.
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). 833 words, ~1,863 tokens.
Download SKILL.mdSave it as
.claude/skills/hipaa-mobile-health/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- hipaa-mobile-health
- description
- Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring. Covers OCR guidance on mobile device PHI, FDA-regulated mobile medical applications, FTC Health Breach Notification Rule for non-HIPAA apps, BYOD policies, and encryption requirements for ePHI on mobile platforms. Keywords: mHealth, mobile health, HIPAA mobile, wearable, remote monitoring, BYOD, mobile device management, app privacy.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- healthcare-privacy
- metadata.tags
- hipaa, mobile-health, mhealth, wearable, remote-monitoring, byod, mobile-device, app-privacy
HIPAA Mobile Health — mHealth Privacy and Security
Overview
Mobile health (mHealth) encompasses the use of mobile devices, applications, wearable sensors, and remote patient monitoring systems to deliver healthcare services and manage health information. OCR has issued specific guidance on HIPAA compliance for mobile devices, recognizing that the proliferation of smartphones, tablets, and wearable health technology creates significant risks to the confidentiality, integrity, and availability of ePHI. The regulatory landscape intersects HIPAA (for covered entities and business associates), FDA regulation (for mobile medical devices/software as a medical device), and FTC jurisdiction (for consumer health apps not covered by HIPAA).
Regulatory Framework
HIPAA Security Rule — Mobile-Relevant Provisions
- §164.310(b): Workstation use — policies specifying the proper functions to be performed and the physical attributes of surroundings for workstations accessing ePHI (includes mobile devices)
- §164.310(c): Workstation security — physical safeguards for workstations accessing ePHI to restrict access to authorized users
- §164.310(d): Device and media controls — policies for receipt, removal, disposal, and re-use of hardware and electronic media containing ePHI
- §164.312(a)(1): Access control — unique user identification, emergency access procedure, automatic logoff, encryption and decryption
- §164.312(a)(2)(iv): Encryption and decryption (addressable) — encrypt ePHI stored on mobile devices
- §164.312(d): Person or entity authentication — verify identity of persons seeking access via mobile
- §164.312(e)(1): Transmission security — protect ePHI transmitted over wireless and cellular networks
OCR Mobile Device Guidance
OCR guidance emphasizes that the Security Rule applies to ePHI on all electronic media, including mobile devices. Key OCR positions:
- Mobile devices used to access, receive, transmit, or store ePHI must comply with Security Rule safeguards
- Lost or stolen unencrypted mobile devices containing ePHI constitute presumed breaches under the Breach Notification Rule
- The use of personal mobile devices (BYOD) does not exempt the entity from HIPAA compliance
FTC Health Breach Notification Rule (16 CFR Part 318)
For health apps and connected devices NOT covered by HIPAA:
- Applies to vendors of personal health records and related entities
- Expanded by FTC in 2023 to cover health apps, fitness trackers, and consumer wearables
- Requires breach notification to consumers, FTC, and (for 500+ individuals) media
- Violations subject to FTC enforcement (up to $50,120 per violation per day as of 2024)
FDA Mobile Medical Applications
- FDA exercises enforcement discretion for most general wellness and health management apps
- Software as a Medical Device (SaMD): FDA regulates apps that perform clinical decision support, diagnostic functions, or meet the definition of a medical device
- FDA does NOT enforce HIPAA but PHI handling in FDA-regulated devices must still comply with HIPAA
Mobile Device Security Requirements
| Requirement | Regulation | Implementation |
|---|---|---|
| Device encryption | §164.312(a)(2)(iv) | Full-disk encryption (AES-256) on all mobile devices accessing ePHI |
| Screen lock / auto-logoff | §164.312(a)(2)(iii) | Maximum 2-minute inactivity timeout; biometric or 6-digit PIN |
| Remote wipe capability | §164.310(d)(2)(iii) | MDM-enabled remote wipe for lost/stolen devices |
| Transmission encryption | §164.312(e)(1) | TLS 1.2+ for all data in transit; VPN for network access |
| App-level authentication | §164.312(d) | Per-app authentication for mHealth applications accessing ePHI |
| Malware protection | §164.308(a)(5)(ii)(B) | Mobile threat defense software; app vetting for sideloading |
| Audit logging | §164.312(b) | MDM audit trails for device access, app usage, data transfers |
| Data backup | §164.308(a)(7) | Automated backup of ePHI on mobile; exclude from consumer cloud backup |
Show full SKILL.md (319 more words)Show less
BYOD Policy Requirements
For organizations permitting personal device use:
- Acceptable use policy: Define permitted PHI activities on personal devices
- MDM enrollment: Require mobile device management enrollment with containerization
- Separation of personal and work data: Use app-level containers or work profiles
- Minimum device standards: OS version requirements, jailbreak/root detection, encryption verification
- Offboarding: Remote wipe of organizational data upon termination; leave personal data intact
- Risk acceptance: Document that BYOD risk has been evaluated per §164.308(a)(1) risk analysis
Wearable and Remote Patient Monitoring
| Device Category | HIPAA Applicability | Key Privacy Considerations |
|---|---|---|
| Prescribed RPM devices (e.g., cardiac monitors) | Yes — CE or BA processes PHI | Encryption at rest and in transit; BAA with device vendor; patient consent for continuous monitoring |
| Provider-issued wearables (e.g., glucose monitors) | Yes — CE or BA processes PHI | Data minimization; defined retention; secure transmission to EHR |
| Consumer wearables (e.g., Fitbit, Apple Watch) | Only if data flows to CE/BA | FTC Health Breach Notification Rule applies if non-HIPAA; HIPAA applies once data enters CE/BA systems |
| Clinical trial wearables | Yes — research use of PHI | IRB oversight; authorization or waiver; de-identification at earliest opportunity |
Enforcement Examples
- Lifespan Health System (2020): $1.04 million — unencrypted stolen laptop; OCR found systemic failure to encrypt ePHI on mobile devices despite multiple prior incidents
- Children's Medical Center of Dallas (2017): $3.2 million — unencrypted BlackBerry lost in 2009 and unencrypted laptop stolen in 2013; OCR cited failure to implement encryption after risk analysis identified the risk
- CardioNet (2017): $2.5 million — stolen unencrypted laptop containing ePHI; OCR found insufficient risk analysis and device/media controls for mobile devices
Integration Points
- hipaa-security-rule: Mobile device requirements are a subset of Security Rule technical and physical safeguards
- hipaa-risk-analysis: Mobile devices must be included in enterprise risk analysis scope
- hipaa-breach-notification: Lost/stolen unencrypted mobile devices trigger breach assessment
- hipaa-employee-training: Workforce training must cover mobile device PHI handling
- hipaa-baa-management: BAAs required with MDM vendors, mHealth app vendors, and RPM device manufacturers that access PHI
© 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/hipaa-mobile-health 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
Hipaa Mobile Health 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 |
|---|---|---|---|---|---|---|
| Hipaa Mobile Health this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| 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 | |
| Fda Consultant Specialistdavila7/claude-code-templates | 33k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
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.
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
ISO Standards Readiness Evidence
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.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Grc Knowledge
mlunato47/claude-grc-plugin
Senior GRC analyst expertise across 18 compliance frameworks — NIST 800-53, FedRAMP (Rev5 + 20x/CR26, KSIs, VDR/VER, Certification Classes A–D), DoD/DoW Impact Levels (IL2–IL6, DISA Cloud SRG), ITAR…
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
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.
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).
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.
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.
Related
Categories
Questions about Hipaa Mobile Health
What does Hipaa Mobile Health do?
Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring. Hipaa Mobile Health is an agent skill from mukul975/Privacy-Data-Protection-Skills. Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring.
When should I use Hipaa Mobile Health?
Hipaa Mobile Health fits situations like: tasks that involve Healthcare and finance regulation.
How do I install Hipaa Mobile Health in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a claude-code`. Or copy the skill folder (skills/privacy/hipaa-mobile-health in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/hipaa-mobile-health in your project. Claude Code loads it when a task matches its description.
How do I install Hipaa Mobile Health in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-mobile-health -a codex`. Or copy the skill folder (skills/privacy/hipaa-mobile-health in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/hipaa-mobile-health in your project. Codex loads it when a task matches its description.
Can I use Hipaa Mobile Health 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 hipaa-mobile-health -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hipaa-mobile-health, .gemini/skills/hipaa-mobile-health, .github/skills/hipaa-mobile-health and .opencode/skills/hipaa-mobile-health in your project.
What does Hipaa Mobile Health need to run?
Going by SKILL.md and its folder, Hipaa Mobile Health needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Hipaa Mobile Health 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 Hipaa Mobile Health 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 Hipaa Mobile Health use?
Hipaa Mobile Health 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 Hipaa Mobile Health use?
About 1.9k tokens (SKILL.md is roughly 7.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 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Hipaa Mobile Health?
Skills that share tags, products or a category with Hipaa Mobile Health: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars) and ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hipaa Mobile Health?
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.