Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Hipaa Incident Response Plan Generator

skill · ECNU-ICALK/AutoSkillLicence not declaredAudited 14 Oct 2026 · source 04e912cff54b

★ 602pushed 157 days agoversion 0.1.0
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 04e912c
602repo stars · whole ECNU-ICALK/AutoSkill

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 04e912cff54b and found no filesystem, network or shell access and no hard-coded secrets. What it does: Generates a comprehensive, HIPAA-compliant Incident Response Plan for medical companies, including team structures, tiered classification systems, threat feeds, handler checklists, SIEM policies, red teaming details,…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Hipaa Incident Response Plan Generator (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/hipaa-incident-response-plan-generator

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

What it tells the agent

Full source on GitHub ↗

Its description: Generates a comprehensive, HIPAA-compliant Incident Response Plan for medical companies, including team structures, tiered classification systems, threat feeds, handler checklists, SIEM policies, red teaming details,…

---
id: "1c88d1df-8deb-4818-86a7-2c79b4ca1690"
name: "HIPAA Incident Response Plan Generator"
description: "Generates a comprehensive, HIPAA-compliant Incident Response Plan for medical companies, including team structures, tiered classification systems, threat feeds, handler checklists, SIEM policies, red teaming details, RACI matrices, and governance processes."
version: "0.1.0"
tags:
  - "HIPAA"
  - "Incident Response"
  - "Security Policy"
  - "Medical"
  - "Compliance"
triggers:
  - "Create a HIPAA incident response plan"
  - "Draft a security incident response policy for a medical company"
  - "Generate a HIPAA compliant IR plan with RACI and exception processes"
  - "Write an incident handler checklist and SIEM policy for healthcare"
  - "Develop a red team and IR team structure for HIPAA compliance"
---

# HIPAA Incident Response Plan Generator

Generates a comprehensive, HIPAA-compliant Incident Response Plan for medical companies, including team structures, tiered classification systems, threat feeds, handler checklists, SIEM policies, red teaming details, RACI matrices, and governance processes.

## Prompt

# Role & Objective
Act as an Information Security Auditor and Policy Writer. Generate a comprehensive Incident Response Plan for a medical company seeking HIPAA compliance. The plan must be detailed and adhere to industry best practices.

# Operational Rules & Constraints
1. **Incident Response Team Structure:** Define roles and responsibilities for a 24/7 operation with at least two to three tiers of responders/handlers. Include necessary skills, experience, and certifications for recruitment.
2. **Executive Summary:** Provide a 3 to 4 paragraph summary explaining why the policy is being written and what it does.
3. **Classification System:** Provide a description of a three to four tiered security incident classification system. P1 must be the most critical, and P3/P4 the least critical. Detail how incidents are classified within this system.
4. **Security Threat Feeds:** Provide a list of recommended security threat feeds (both paid and publicly available). In brackets, provide the reasoning for each suggestion.
5. **Incident Handler Checklist:** Present the checklist as a series of questions. Use current best practices and do not copy from the SANS Incident Handler Checklist.
6. **SIEM Policy:** Recommend SIEM setup including mandatory feeds (vulnerability scan data, asset information, network information, EDR/endpoint information, WAF info). Recommend additional feeds. Recommend an AWS data lake architecture (using AWS services) and a specific tool/service for developing custom dashboards for the IR team.
7. **Red Team/Threat Hunting:** Provide a detailed description of the threat hunting team (Manager and threat hunters, 2-3 tiers). Include roles, responsibilities, years of work experience, skills, and certifications. Provide a description/summary for executives on what a red team does and how it complements the blue team.
8. **RACI Chart:** Create a RACI matrix listing all IR activities on the vertical and roles on the horizontal. Include Legal, Executives, and Management functions.
9. **Governance Roles:** Describe roles and responsibilities for Legal, Executives, Management, and the CISO.
10. **Exception Process:** Document the exception process covering: Who qualifies, who approves, the process for granting an exception, required audit artifacts, retention period, and access rights.
11. **Change Process:** Document the change process covering: Who can request, who approves, the process for granting a change, required audit artifacts, retention period, and access rights.

# Communication & Style Preferences
- Be as detailed as possible within character limits.
- Maintain a professional, audit-ready tone suitable for HIPAA compliance.

## Triggers

- Create a HIPAA incident response plan
- Draft a security incident response policy for a medical company
- Generate a HIPAA compliant IR plan with RACI and exception processes
- Write an incident handler checklist and SIEM policy for healthcare
- Develop a red team and IR team structure for HIPAA compliance

Excerpt, first 4,150 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 04e912c

Download folder ↗
git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

The author documents no install command, so this uses the repository directly. Our verdict covers commit 04e912cff54b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 04e912cff54b

Similar skills

Questions about Hipaa Incident Response Plan Generator

What does the Hipaa Incident Response Plan Generator skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Hipaa Incident Response Plan Generator safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Hipaa Incident Response Plan Generator access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (04e912cff54b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.