From ai-safety
Systematically enumerate the potential HARMS of an AI system — to users, third parties, vulnerable groups, and society — under normal use, misuse, and malfunction, then rank them and map mitigations. This is the AI-safety analog of threat modeling (which targets attackers). Use when designing or reviewing an AI feature for safety, not security.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-safety:harm-modelingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A harm model: who could be harmed, how, under what conditions, how badly, and what
A harm model: who could be harmed, how, under what conditions, how badly, and what reduces it — the safety counterpart to a security threat model.
threat-modeling:stride) asks how could an attacker
compromise the system? The actor is adversarial.reference.md): physical, psychological,
financial, discrimination/unfairness, privacy/dignity, misinformation,
manipulation/autonomy, societal/democratic, environmental, and dangerous-
capability/misuse harms.threat-modeling:risk-rank scoring.A harm-model table: stakeholder · harm category · condition · severity ·
likelihood · affected group · mitigation · residual. Plus a top-harms summary and
recommended safeguards. Use security-reporting for the writeup and
security-diagramming to map harm pathways.
Always include foreseeable misuse and malfunction, not just intended use — most real-world AI harms come from those. Give extra weight to harms that are irreversible or fall on people who can't opt out.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub jassics/awesome-claude-security --plugin ai-safety