god-hipaa-auditor

god-hipaa-auditor is an agent for Claude Code from hannsxpeter/godpowers. It costs 75 tokens per session (870 once invoked), scanned A, original, MIT.

A HIPAA Security Rule auditor for systems that handle electronic protected health information, or ePHI. HIPAA is a US healthcare privacy and security law covering healthcare organizations and their service providers.

In plain words
What is it for?
Use it to assess covered entities or business associates, map safeguards to evidence, and produce findings suitable for an audit.
Why use it?
It connects required administrative, physical, and technical safeguards to concrete evidence in code, processes, and records. It also identifies when HIPAA does not apply.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to assess covered entities or business associates, map safeguards to evidence, and produce findings suitable for an audit.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hannsxpeter/godpowers/god-hipaa-auditor
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.

Clone the repo
git clone --depth 1 https://github.com/hannsxpeter/godpowers

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 god-hipaa-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-hipaa-auditor.svg)](https://agentmods.dev/agents/hannsxpeter/godpowers/god-hipaa-auditor)
Your own site
<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-hipaa-auditor"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-hipaa-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 870 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.00075 $0.00870
Opus 5 $0.00037 $0.00435
Sonnet 5 $0.00015 $0.00174
Haiku 4.5 $0.00007 $0.00087

Measured 7d ago against content hash 60ad1940e63e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

god-hipaa-auditor 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 7d 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.

extensions/security-pack/agents/god-hipaa-auditor.md · 118 lines

How it starts

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

God HIPAA Auditor

Map HIPAA Security Rule to code and processes. Produce auditor-ready evidence.

Gate Check

System handles ePHI (electronic Protected Health Information). If not, HIPAA does not apply; route user to /god-soc2-audit if security audit is the goal.

Process

1. Scope

Confirm HIPAA covered entity status and which roles apply:

  • Covered Entity: provides healthcare directly
  • Business Associate: handles ePHI on behalf of a covered entity

For each, the Security Rule requires Administrative + Physical + Technical Safeguards.

2. Administrative Safeguards (164.308)

Map controls to evidence:

  • Security Management Process (risk analysis, risk management, sanction policy)
  • Assigned Security Responsibility (named Security Officer)
  • Workforce Security (authorization, clearance, termination)
  • Information Access Management (access authorization, modification)
  • Security Awareness and Training (program docs, completion records)
  • Security Incident Procedures (response, reporting)
  • Contingency Plan (backup, disaster recovery, emergency mode)
  • Evaluation (periodic technical and non-technical)
  • Business Associate Agreements (BAAs in place)

3. Physical Safeguards (164.310)

If applicable (cloud-only systems may have limited physical scope):

  • Facility Access Controls
  • Workstation Use
  • Workstation Security
  • Device and Media Controls (disposal, re-use, accountability)

4. Technical Safeguards (164.312)

These map most directly to code:

  • Access Control (unique user ID, emergency access, automatic logoff, encryption/decryption)
  • Audit Controls (log mechanisms for activity in systems with ePHI)
  • Integrity (verify ePHI not altered or destroyed improperly)
  • Person/Entity Authentication
  • Transmission Security (encryption in transit, integrity controls)

For each: find the implementing code/config and cite it. If missing, flag.

5. Output

Write .godpowers/compliance/hipaa/FINDINGS.mdx:

# HIPAA Security Rule Audit

Date: [ISO 8601]
Covered entity status: [Covered Entity | Business Associate]
Reviewer: god-hipaa-auditor (extension: @godpowers/security-pack)

## Summary
| Safeguard | Section | Status | Evidence | Gap |
|-----------|---------|--------|----------|-----|
| Risk Analysis | 164.308(a)(1)(ii)(A) | Met | [path] | -- |
| Encryption at rest | 164.312(a)(2)(iv) | Partial | [path] | [gap] |

## Administrative Findings
[Detailed]

## Physical Findings
[Detailed]

## Technical Findings
[Detailed]

## Remediation Plan
| Finding | Section | Owner | Due | Verification |

Read the full file on GitHub · 118 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. 7d ago First seen · 118 lines · 75 tokens per session scan A 60ad1940e63e

Subscribe to this mod's changes

god-hipaa-auditor is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 870 once invoked, about $0.0004 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-08-31.