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 ThomasMoreAI/legal-skills-open --skill medical-liability-defensegit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/medical-liability-defense)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/medical-liability-defense"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/medical-liability-defense/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/thomasmoreai/legal-skills-open/medical-liability-defense"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/medical-liability-defense.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.00065 | $0.02106 |
| Opus 5.5 | $0.00026 | $0.00842 |
| Sonnet 5.5 | $0.00013 | $0.00421 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
medical-liability-defense 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 24d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/health-medical-legal:medical-liability-defense
Triage de ação por erro médico. Não é parecer de mérito final — é leitura estruturada para triagem, com recomendações de estratégia defensiva.
Cobre:
- Identificação da alegação (diagnóstico incorreto? Erro cirúrgico? Falta de consentimento? Abandono?)
- Padrão de cuidado (era um padrão de meio ou resultado? Qual é o padrão vigente?)
- Culpa sob CC Arts. 186/927/951 [modelo conhecimento — verificar].
- Nexo causal (a conduta causou o dano? Há eventos intermediários que quebram a cadeia?)
- Qualidade do termo de consentimento informado (estava adequado? Documentado?)
- Quesitos para perícia médica (o que perguntar ao perito?).
- Responsabilidade solidária do hospital (Lei 9.656 se envolver operadora [modelo conhecimento — verificar], ou Código Civil/CDC se consumidor [modelo conhecimento — verificar]).
- Defesa estratégica (quais são nossas melhores defensivas? Ordem de prioridade?).
Output: triage rating (forte, debatível, fraco), matriz de defensivas, recomendação de postura, quesitos sugeridos para perícia.
Matter context
Check ## Matter workspaces in CLAUDE.md. If enabled, load active matter context and write outputs to matter folder. If not enabled, write to ~/.claude/plugins/config/claude-for-legal/health-medical-legal/inbound/ with date slug.
Purpose
Medical malpractice claims have a specific anatomy: allegation of breach of standard of care, causation, and damages. This skill reads the demand or complaint, maps the anatomy, and surfaces which pieces are weak.
A triage read, not an opinion. The team decides whether to fight, settle, or watch.
Premissa de jurisdição (Brasil)
Responsabilidade civil por erro médico — Código Civil (Lei 10.406/2002) Arts. 186–405:
- Art. 186: Quem causa dano a outrem fica obrigado a repará-lo.
- Arts. 389–405: Obrigação de meio vs. resultado. A maioria das obrigações médicas são de meio, não resultado — o médico se obriga a usar diligência e conhecimento, não a curar [modelo conhecimento — verificar]. Exceção: algumas intervenções (cirurgia estética, implante com garantia) podem ser de resultado.
- Art. 927: Culpa (negligência, imprudência, imperícia) é elemento necessário [modelo conhecimento — verificar].
- Arts. 951: Profissional liberal responde por culpa [modelo conhecimento — verificar].
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.
- 24d ago First seen · 227 lines · 65 tokens per session scan A bb7a4f4fe796
medical-liability-defense is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 65 tokens to every session and 2,106 once invoked, about $0.0003 per session on Opus 5.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-10-04.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…