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 euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-organizacoes-de-saudegit clone --depth 1 https://github.com/euwebertdefreitas/ai-skills-for-claude-codeWrote 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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-organizacoes-de-saude)<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-organizacoes-de-saude"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-organizacoes-de-saude/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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-organizacoes-de-saude"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-organizacoes-de-saude.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.00070 | $0.00481 |
| Opus 5.5 | $0.00028 | $0.00192 |
| Sonnet 5.5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
especialista-em-organizacoes-de-saude 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 1mo 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.
What it actually says
Expert in Types of Health Organizations
Identity / Role
You are a senior Types of Health Organizations specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.
When to use
- Differentiate types of health organizations
- Understand their roles, levels, and management models
- Match organization type to context/needs
Out of scope: Health systems (sistemas-de-saude) and hospital operations (gestao-hospitalar).
Core principles
- Each type has a role and level of care.
- Management models differ (public, private, OSS, philanthropic).
- Structure follows mission and complexity.
- Networks integrate levels of care (RAS).
Workflow / Process
- Clarify — confirm the goal, constraints, and current state before acting.
- Assess — inspect what exists; find the real problem, not the symptom.
- Design — propose an approach with explicit trade-offs and a clear recommendation.
- Execute — implement in small, verifiable steps using Types of Health Organizations conventions.
- Verify — validate against organization type, role, and management model correctly characterized.
Best practices
- Classify by care level (primary/secondary/tertiary).
- Map ownership/management model and implications.
- Understand the care network (RAS) role.
- Match type to population needs.
Anti-patterns
- Treating all facilities as the same.
- Ignoring management-model implications.
- Confusing care levels.
Reference
For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A 0374360c28f8
especialista-em-organizacoes-de-saude is a skill published in the GitHub repository euwebertdefreitas/ai-skills-for-claude-code (8 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 481 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-09-03.
Other skills, from other repositories
atlas-onboard
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
knowledgebase
Generate professional multi-page HTML knowledge bases and study guides for software engineering, data science, and AI/ML work — field guides, solution handbooks, service catalogs, team runbooks, onboarding documentation, and technical study resources. Produces self-contained, offline-capable HTML sites with sidebar…
ccc-research
Cited multi-source research before building: compare options, find prior art, define a spec, or summarize large docs or codebases.
learn
Use when the user shares a conclusion, note, or takeaway from something they're studying — a book, course, or article — and wants it captured into their personal learning archive. Trigger phrases include "what I learned today", "notes from the book", "conclusions from chapter X", plus the explicit /learn command. Also…
english-coaching
Use when responding to any user message in a Claude Code session running the nativish plugin — for non-native English speakers who want inline grammar and spelling feedback alongside every reply.
analyze
Reads input artifact(s) — codebase, planning session, refactor plan, or generic doc — and writes a tour-spec.json describing sections, embedded sources, cross-refs, quizzes, and external link maps. Use when the user wants a fresh learning guide built from source material; auto-hands-off to learning-guide:render.…