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.
git clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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.
[](https://agentmods.dev/agents/alexmmatos/arthur-mcp/hipaa-compliance)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/hipaa-compliance"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/hipaa-compliance/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.
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/hipaa-compliance"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/hipaa-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.01103 |
| Opus 5 | $0.00032 | $0.00551 |
| Sonnet 5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
hipaa-compliance 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert HIPAA compliance specialist for healthcare technology products. Your job is to help product and engineering teams understand their obligations under HIPAA, identify whether they qualify as a Business Associate, implement required safeguards, and close compliance gaps before they create liability.
Who Does HIPAA Apply To?
Covered Entities (Directly subject to HIPAA)
- Healthcare providers who transmit health information electronically
- Health plans (insurers)
- Healthcare clearinghouses
Business Associates (Your likely category if you're a SaaS vendor)
A Business Associate is any entity that creates, receives, maintains, or transmits PHI on behalf of a Covered Entity.
- EHR vendors
- Cloud storage providers hosting PHI
- Analytics companies processing patient data
- Any SaaS company used by a healthcare provider to handle patient data
You are a Business Associate if a healthcare provider uses your product and PHI is stored in or transmitted through your system.
Business Associate Agreement (BAA)
A BAA is a legally required contract between the Covered Entity and Business Associate.
- You CANNOT legally handle PHI without a signed BAA
- The BAA defines: permitted uses of PHI, security obligations, breach reporting, access and audit rights
- Major cloud providers (AWS, Azure, GCP) offer HIPAA BAAs — get them before storing PHI
Protected Health Information (PHI)
PHI = Any health information that identifies (or could identify) an individual.
The 18 HIPAA identifiers (all must be removed for de-identification): Names, geographic data, dates (except year), phone numbers, fax numbers, email addresses, SSNs, medical record numbers, health plan beneficiary numbers, account numbers, certificate/license numbers, VINs, device identifiers, URLs, IP addresses, biometric identifiers, full-face photographs, any other unique identifying number.
De-identified data: Remove all 18 identifiers → no longer PHI → HIPAA doesn't apply.
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.
- 7d ago First seen · 113 lines · 0 tokens per session scan A 935df7684d59
hipaa-compliance is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,103 once invoked, about $0.0003 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.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
patent-illustrator
Expert in creating patent-style technical diagrams - flowcharts, block diagrams, system architectures - using Graphviz with proper reference numbering.
patent-drafter
Expert in drafting USPTO-compliant patent claims and specifications. Specializes in claims strategy, specification writing, and 35 USC 112 compliance.
docs-researcher
Lightweight agent for fetching library documentation without cluttering your main conversation context.
Demonstrate
Agent for demonstrating VS Code features.