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 tatagoncalvesof/imperatriz-toolkit --skill anamnese-mentoradagit clone --depth 1 https://github.com/tatagoncalvesof/imperatriz-toolkitWrote 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/tatagoncalvesof/imperatriz-toolkit/anamnese-mentorada)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/anamnese-mentorada"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/anamnese-mentorada/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/tatagoncalvesof/imperatriz-toolkit/anamnese-mentorada"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/anamnese-mentorada.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.00278 | $0.04649 |
| Opus 5 | $0.00139 | $0.02325 |
| Sonnet 5 | $0.00056 | $0.00930 |
| Haiku 4.5 | $0.00028 | $0.00465 |
Grade A, and why
anamnese-mentorada 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 11d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anamnese Mentorada — Porta de Entrada da Travessia Imperatriz
Esta e a primeira skill que roda quando uma mentorada nova entra na Travessia Imperatriz. E o exame medico completo que abastece todas as outras skills do ecossistema. Sem anamnese feita, nenhuma decisao estrategica boa sai. Sem anamnese honesta, a Tata erra o tom da call.
Filosofia central
Anamnese mal feita = mentoria mal feita. A Tata nao chuta. A Tata diagnostica.
Anamnese vem da medicina: e o relato que o paciente faz antes de qualquer exame ou tratamento. Sem anamnese boa, o medico erra remedio. Sem anamnese boa, a Tata erra plano de 6 meses.
A skill nao gera plano. A skill abastece os planos das outras skills. E o ato 0. A camada de dados crus que vira ouro depois.
Quando usar
- Mentorada acabou de fechar contrato e entra hoje na Travessia
- Tata vai fazer pre-call de entrada e precisa de briefing
- Mentorada antiga voltou pra second mentorship — refazer anamnese
- Tata quer ressuscitar dossie de mentorada parada ha 6+ meses
- Antes de rodar
/perfil-mentoradaou/imperio-diagnostico— anamnese e pre-requisito - Tata vai delegar onboarding pra time (Severino) — formulario sai daqui
Diferenca entre anamnese, dossie, perfil e diagnostico
- Anamnese = entrevista de entrada. Coleta crua de fatos. UMA VEZ.
- Perfil = classificacao da mentorada (Construtora / Frustrada / Premium / etc) baseada na anamnese.
- Dossie = ficha viva que evolui durante a mentoria toda (atualizada toda call).
- Diagnostico = FRIO + DOMINIO + PENTA aplicado sobre a anamnese pra gerar plano.
A skill foca em anamnese. Se a Tata pedir plano, classificacao ou diagnostico, redirecionar pras skills corretas.
OS 4 MODOS DE OPERACAO
A skill roda em 4 modos declaraveis. Se a Tata nao declarar, perguntar "formulario, call, auto ou validar?".
--formulario
Quando: Tata quer enviar pra mentorada preencher offline (email/WA antes da call).
Output: arquivo HTML standalone (sem dependencia externa) com 8 blocos navegaveis, voz Tata (provocativa, direta, intima), botao "exportar JSON" no final.
Entrega: mentorada baixa, preenche, exporta JSON, manda de volta. Tata roda /anamnese-mentorada --validar no JSON recebido.
What ships with it
5 files 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.
- 11d ago First seen · 357 lines · 278 tokens per session scan A c33f1459b993
anamnese-mentorada is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 278 tokens to every session and 4,649 once invoked, about $0.0014 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-31.
Other skills, from other repositories
fp-brief
First-principles briefing from technical documents. Use when: understanding why decisions were made, onboarding to feature reasoning, reviewing decision chains, explaining doc from first principles. Not for: PM/CTO summary (use project-brief), pre-doc analysis (use feasibility-study), code explanation (use…
codex-explain
Explain complex code via Codex exec. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth.
sharingan
Replicate knowledge from any source as sd0x-dev-flow skill definition. Use when: copying skills from repos, adapting patterns from articles/papers/code, converting knowledge to skill format. Not for: research without skill output (use deep-research), creating skills from scratch (use skill-creator), project onboarding…
creating-explainers
Use when creating an interactive explainer - a single self-contained HTML page with hand-built Canvas figures. Handles source-file explainers, topic-driven research explainers, and mixed intake where files provide the spine and research adds support. Trigger phrases include "make an explainer", "turn this paper into…
explaining-codebases
Use when creating an interactive explainer about a codebase, repository, or source files. Handles onboarding overviews, architecture maps, and deep-dives on real implementation paths. Trigger phrases include "explain this codebase", "interactive guide to this repo", "walk through how X works in the code", or…
openehr-assistant
This skill should be used when a conversation touches openEHR outside a task owned by a dedicated skill — e.g. "what is an archetype?", "how do openEHR templates work?", "which composition category fits this data?", "find me a guide on X", "where do I start with openEHR modeling?" — or names openEHR concepts (ADL…