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/essentials-claude-codeWrote 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/essentials-claude-code/hipaa-compliance)<a href="https://agentmods.dev/agents/alexmmatos/essentials-claude-code/hipaa-compliance"><img src="https://agentmods.dev/badge/agents/alexmmatos/essentials-claude-code/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/essentials-claude-code/hipaa-compliance"><img src="https://agentmods.dev/badge/agents/alexmmatos/essentials-claude-code/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.00000 | $0.01103 |
| Opus 5.5 | $0.00000 | $0.00441 |
| Sonnet 5.5 | $0.00000 | $0.00221 |
| Haiku 4.5 | $0.00000 | $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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 113 lines · 0 tokens per session scan A 935df7684d59
hipaa-compliance is an agent published in the GitHub repository alexmmatos/essentials-claude-code (1 stars, last pushed 3mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,103 tokens. 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
legal-policy
Legal, Compliance, and Policy Validator.
reviewer
Fills a loop's reviewer seat with an adversarial Claude critique when the dispatching skill has seated Claude instead of Codex for this run (Codex's rate-limit budget is running ahead of the elapsed share of its window). Reads the target from disk exactly as the prompt names it, looks for ways to break it, and writes…
documenter
Edits one documentation file in place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (new file: scaffolds from sibling docs' style, with TODOs where information is missing). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc…
implementer
Executes one planned implementation step end-to-end: reads context, makes the minimum change, runs obvious verification, reports the diff. Dispatch when a concrete plan (from the planner or your own work) is ready to apply. Context: A plan exists and the next task is queued. user: "Run task 3 from the plan."…
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
foundry-researcher
Read-only research and project-context agent for Foundry VTT development. Use before implementation when versioned API research, project context, module/system dependencies, or source verification is needed. Does not edit code. Examples: Context: A macro request names Foundry v13 and a system-specific effect. user…