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.
npx skills add curiositech/some_claude_skills --skill crisis-response-protocolgit clone --depth 1 https://github.com/curiositech/some_claude_skillsWrote 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/skills/curiositech/some_claude_skills/crisis-response-protocol)<a href="https://agentmods.dev/skills/curiositech/some_claude_skills/crisis-response-protocol"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/crisis-response-protocol/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/skills/curiositech/some_claude_skills/crisis-response-protocol"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/crisis-response-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.03050 |
| Opus 5 | $0.00024 | $0.01525 |
| Sonnet 5 | $0.00010 | $0.00610 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
crisis-response-protocol 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 10d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crisis Response Protocol
This skill helps you implement safe crisis intervention features for the AI coaching system, following mental health best practices.
When to Use
✅ USE this skill for:
- Implementing crisis detection in recovery/mental health apps
- Building safety planning features
- Integrating hotline and emergency resource displays
- Designing risk assessment interfaces
- Creating escalation protocols for AI chat systems
❌ DO NOT use for:
- Responding to an actual crisis yourself → Call 988 or emergency services
- General mental health content → use
sober-addict-protectororrecovery-coach-patterns - Medical advice or diagnosis → Always defer to licensed professionals
- Replacing human crisis counselors → AI should augment, never replace
Critical Safety Principle
AI should NEVER be the sole responder in acute crisis situations. Always provide pathways to human support and emergency services.
Crisis Detection
Risk Indicator Categories
interface RiskIndicators {
// PRIMARY - Immediate escalation required
primary: {
suicidalIdeation: string[]; // "want to die", "end it all"
selfHarmIntent: string[]; // "hurt myself", "cutting"
homicidalIdeation: string[]; // "hurt someone"
activeSubstanceEmergency: string[]; // "overdosed", "can't stop"
};
// SECONDARY - Elevated monitoring
secondary: {
severeDepression: string[]; // "hopeless", "no point"
panicSymptoms: string[]; // "can't breathe", "heart racing"
psychoticSymptoms: string[]; // "hearing voices"
severeAnxiety: string[]; // "terrified", "losing control"
};
// TERTIARY - Check-in triggers
tertiary: {
isolationPatterns: string[]; // "no one cares", "alone"
substanceRelapse: string[]; // "started using", "slipped"
hopelessness: string[]; // "never get better"
};
}
Detection Implementation
// src/lib/ai/crisis-detection.ts
export interface CrisisAssessment {
level: 'none' | 'low' | 'medium' | 'high' | 'critical';
indicators: string[];
recommendedAction: CrisisAction;
timestamp: Date;
}
export type CrisisAction =
| 'continue_conversation'
| 'gentle_check_in'
| 'safety_resources'
| 'crisis_protocol'
| 'emergency_escalation';
export function assessCrisisLevel(
messageContent: string,
conversationHistory: Message[],
userCheckInHistory: CheckIn[]
): CrisisAssessment {
const indicators: string[] = [];
let level: CrisisAssessment['level'] = 'none';
// Check primary indicators (critical)
if (hasPrimaryIndicators(messageContent)) {
level = 'critical';
indicators.push('primary_risk_detected');
}
// Check secondary indicators
if (hasSecondaryIndicators(messageContent)) {
level = level === 'none' ? 'high' : level;
indicators.push('secondary_risk_detected');
}
// Check pattern indicators from history
if (hasWorseningPattern(userCheckInHistory)) {
level = level === 'none' ? 'medium' : level;
indicators.push('worsening_trend');
}
// Check conversation escalation
if (hasEscalatingDistress(conversationHistory)) {
level = level === 'none' ? 'medium' : level;
indicators.push('escalating_distress');
}
return {
level,
indicators,
recommendedAction: getRecommendedAction(level),
timestamp: new Date(),
};
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 457 lines · 49 tokens per session scan A 816c9cbe69f1
crisis-response-protocol is a skill published in the GitHub repository curiositech/some_claude_skills (218 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 3,050 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…