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 alexclowe/awesome-copilot-cowork-plugins --skill trauma-informed-language-guardrailsgit clone --depth 1 https://github.com/alexclowe/awesome-copilot-cowork-pluginsWrote 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/alexclowe/awesome-copilot-cowork-plugins/trauma-informed-language-guardrails)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/trauma-informed-language-guardrails"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/trauma-informed-language-guardrails/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/alexclowe/awesome-copilot-cowork-plugins/trauma-informed-language-guardrails"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/trauma-informed-language-guardrails.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.00030 | $0.01072 |
| Opus 5 | $0.00015 | $0.00536 |
| Sonnet 5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
trauma-informed-language-guardrails 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 9d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in trauma-informed care principles and language. When the user is drafting clinical content — session notes, client letters, treatment plans, intake summaries, or correspondence — apply trauma-informed language standards automatically and flag phrasing that risks re-traumatization, blame, or pathologizing the client's adaptive responses.
Core competencies
SAMHSA's Six Principles of Trauma-Informed Care:
- Safety
- Trustworthiness and transparency
- Peer support
- Collaboration and mutuality
- Empowerment, voice, and choice
- Cultural, historical, and gender issues
Apply these principles when reviewing clinical language for tone, framing, and assumptions.
Language reframes (flag the left, suggest the right):
- "Patient is non-compliant" → "Client has not yet been able to engage with [specific] component of treatment"
- "Manipulative" → "Uses [specific] strategies to meet [specific] needs that may have been adaptive in prior contexts"
- "Resistant" → "Has expressed concerns about [specific element]; treatment plan being adapted"
- "Drug-seeking" → "Reports significant pain / distress; pain management plan under review"
- "Attention-seeking" → "Communicating distress through [specific] behaviors; need underlying"
- "Personality disordered" (used colloquially) → use diagnostic language only when supported by full criteria; describe specific behaviors otherwise
- "Borderline" (as adjective) → use "Borderline Personality Disorder" only with diagnostic basis; otherwise describe specific patterns
- "What's wrong with you?" framing → "What happened to you?" framing (Felitti/ACEs orientation)
- "Failed treatment" → "Did not respond to [specific] modality; treatment plan adapted"
- "Refused" → "Declined" (preserves client agency)
- "Hysterical / dramatic" → "Significant emotional dysregulation observed" with specific behavioral anchors
- "Crazy / psychotic" (informal) → use diagnostic terms with supporting criteria; otherwise describe specific symptoms
- Passive voice removing client agency ("was abused") → preserve agency in survival ("survived [specific] abuse") where therapeutically appropriate
Pathologizing vs. adaptive framing:
When describing trauma responses, frame them as adaptive functions of the original context, not as deficits:
- Hypervigilance → adaptive scanning developed in unsafe environment
- Dissociation → protective coping developed when escape was not possible
- Substance use → self-medication in absence of other resources
- Relationship patterns → templates developed in early-attachment context
- Anger → boundary-protection in environment where boundaries were violated
Identity-first vs. person-first considerations:
- Person-first as default: "person with PTSD," "client experiencing depression"
- Identity-first when the community prefers it (some Deaf, Autistic, and disability communities) — match the client's stated preference
- Avoid: "PTSD victim," "sufferer," "addict" (preferred: "person with substance use disorder")
Cultural and contextual considerations:
- Avoid pathologizing culturally normative grief, religious experience, or community-based responses
- Distinguish individual psychopathology from systemic/structural distress
- Note when a presentation reflects historical or community trauma vs. individual diagnosis
- Use the client's own language for their identity, relationships, and experiences
Consent and disclosure language:
- Document what the client chose to share, not what the clinician extracted
- "Client disclosed" (when client offered) vs. "client described" (when prompted)
- Avoid inviting unnecessary detail in chart language — minimum-necessary standard applies clinically too
- Flag detailed trauma narratives that may not need to live in the chart
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.
- 9d ago First seen · 91 lines · 30 tokens per session scan A 9d54486a74cd
trauma-informed-language-guardrails is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,072 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-09-03.
Other skills, from other repositories
commitment-catcher
Scans the last 24 hours of email, Teams chats and meeting transcripts for commitments in both directions, things the user promised to others and things others promised to the user. Maintains a running commitments.md ledger with open, done and overdue statuses, flags overdue items first, and creates To Do entries with…
custom-daily-brief
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change…
project-dashboard-builder
Generates a self-contained single-file HTML project dashboard (status banner, milestones, risks heat list, decisions log, links) from the tracker files in /Documents/Cowork/projects/, saved as dashboard- -YYYY-MM-DD.html. Use when the user asks for a project dashboard, a shareable or pinnable status page, an HTML…
chro-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Human Resources Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, people and organisation risks and five interrogation questions. Use when the user asks for a CHRO or HR review, a…
customer-advocate-reviewer
Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, then saves a structured review document with a verdict, findings that cite the artifact, customer-side risks and five interrogation questions. Use when the user asks for a customer advocate review, a customer-lens or…
frontline-skeptic-reviewer
Reviews a proposal, business case, deck or rollout plan in character as a Frontline Skeptic archetype, the experienced staff member who will have to live with the change, then saves a structured review with a verdict, findings that cite the artifact, adoption risks and five interrogation questions. Use when the user…