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 reuniao-de-resultadogit 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/reuniao-de-resultado)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado/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/reuniao-de-resultado"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado.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.00237 | $0.03016 |
| Opus 5 | $0.00118 | $0.01508 |
| Sonnet 5 | $0.00047 | $0.00603 |
| Haiku 4.5 | $0.00024 | $0.00302 |
Grade A, and why
reuniao-de-resultado 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 12d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reunião de Resultado — Skill Imperatriz
Skill proprietária da Tata Gonçalves. Constrói o sistema completo de Reunião de Resultado pra qualquer negócio — diagnóstico, estrutura, condução, implementação e primeira reunião — em pacote pronto pra usar (HTML + arquivos no vault).
Overview
Reunião de Resultado é o ritual gerencial que transforma reunião que não decide nada em reunião que faz dinheiro. O método tem 6 blocos sequenciais (diagnóstico → estrutura → core → condução → implementação → primeira reunião) e essa skill empacota TUDO em entregáveis prontos pra uma empresária implementar na semana que vem.
Dois modos de uso — escolha um no início da conversa:
- Modo Transcrição — a usuária cola transcrição de uma reunião que já faz hoje. A skill diagnostica os 7 sintomas, mapeia os erros do bloco 5, e entrega plano de transformação personalizado.
- Modo Do Zero — a usuária ainda não tem reunião estruturada. A skill faz entrevista curta (5 perguntas) e monta o sistema completo do zero.
Em ambos os modos, o output final é o mesmo: HTML standalone + 14 arquivos no Obsidian Vault.
Workflow Decision Tree
1. Detectar modo (perguntar se ainda não está claro)
├── Modo A: TRANSCRIÇÃO
│ ├── Aceitar transcrição
│ ├── (opcional) sugerir /transcript-fixer se vier crua de STT
│ ├── Diagnosticar 7 sintomas (references/bloco-1-diagnostico.md)
│ ├── Mapear contra 7 erros (references/bloco-5-implementacao.md)
│ ├── Resumir gaps em 1 página
│ └── Seguir pra construção do pacote
│
└── Modo B: DO ZERO
├── 5 perguntas de briefing (ver "Briefing Mínimo" abaixo)
├── (opcional) sugerir /mecanismo-unico se a usuária não souber
│ o que diferencia o negócio dela — ajuda a escolher os 2-3
│ indicadores que importam
└── Seguir pra construção do pacote
2. Construir pacote (sempre igual nos dois modos)
├── Ler os 6 references/ pra absorver método
├── Personalizar templates de assets/vault-templates/ com dados do briefing/diagnóstico
├── Personalizar assets/dashboard-template.html
├── Passar comunicado pro grupo + roteiro 1ª reunião por /voz-humana-br
│ (obrigatório — não entregar texto sem humanizar)
└── Salvar tudo no destino
3. Entregar
├── Vault: ~/Documents/Obsidian Vault/03 - Projetos/Reuniao-Resultado-{NEGOCIO}/
├── HTML: mesma pasta, arquivo dashboard.html
└── Resumo final no chat: lista dos 15 arquivos + próxima ação
4. Modo pós-construção (se a usuária voltar depois)
├── "Auditar minha reunião de ontem" → roda diagnóstico em transcrição nova
├── "Refazer ata" → atualiza só o template de ata
├── "Plano de ação pra meta X em risco" → gera só o plano (bloco 3)
└── "Roteiro pra próxima reunião" → gera só o roteiro
What ships with it
21 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.
- assets/dashboard-template.html 27 KB
- assets/vault-templates/00-Overview.md 3.0 KB
- assets/vault-templates/01-Diagnostico-7-Sintomas.md 2.5 KB
- assets/vault-templates/02-Os-2-3-Indicadores.md 2.8 KB
- assets/vault-templates/03-Agenda-Sagrada.md 2.6 KB
- assets/vault-templates/04-Checklist-6-Passos.md 3.3 KB
- assets/vault-templates/05-Template-Ata.md 2.2 KB
- assets/vault-templates/06-FCA-5-Porques.md 3.3 KB
- assets/vault-templates/07-Plano-Acao-Meta-Risco.md 2.5 KB
- assets/vault-templates/08-Feedback-Sem-Destruir.md 3.0 KB
- assets/vault-templates/09-Cobrar-Sem-Ser-Toxico.md 4.0 KB
- assets/vault-templates/10-Efeito-Brio.md 3.8 KB
- assets/vault-templates/11-7-Erros-Que-Arruinam.md 3.7 KB
- assets/vault-templates/12-Comunicado-Grupo-Hoje.md 3.4 KB
- assets/vault-templates/13-Roteiro-Primeira-Reuniao.md 5.0 KB
- references/bloco-1-diagnostico.md 4.7 KB
- references/bloco-2-estrutura.md 5.3 KB
- references/bloco-3-core.md 8.0 KB
- references/bloco-4-conducao.md 7.5 KB
- references/bloco-5-implementacao.md 7.1 KB
- references/bloco-6-primeira-reuniao.md 7.9 KB
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.
- 12d ago First seen · 156 lines · 237 tokens per session scan A 9607ec7644db
reuniao-de-resultado is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 237 tokens to every session and 3,016 once invoked, about $0.0012 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
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
req-analyze
A requirements-analysis tool that breaks a problem into needs, stakeholders, and priorities before a technical solution is chosen.
recap-ask
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap- .md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).