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 sucessao-imperatrizgit 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/sucessao-imperatriz)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/sucessao-imperatriz"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/sucessao-imperatriz/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/sucessao-imperatriz"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/sucessao-imperatriz.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.00404 | $0.03831 |
| Opus 5 | $0.00202 | $0.01916 |
| Sonnet 5 | $0.00081 | $0.00766 |
| Haiku 4.5 | $0.00040 | $0.00383 |
Grade A, and why
sucessao-imperatriz 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sucessao Imperatriz — Pilar 7 (Tribo) da Travessia
Skill operadora do programa de Sucessao da Travessia Imperatriz. Pos-Imperatriz Plena (12+ meses ativa), conduz a mentorada por 3 caminhos formais de continuidade dentro do ecossistema Tata Goncalves.
Filosofia central
Imperatriz nao para — evolui.
Sucessao nao e saida. E elevacao de nivel. A Imperatriz Plena que cumpriu 12+ meses ativa nao "termina" a Travessia — ela escolhe COMO continua a contribuir e a colher do imperio compartilhado. Sair sem sucessao formal e desperdicio de ativo. Ficar parada e regressao. O 3o caminho e o caminho real.
Tres principios duros:
- Nao existe ex-Imperatriz Plena ativa — ou ela esta na Travessia, ou ela esta numa das 3 sucessoes. Limbo nao e opcao oferecida.
- Sucessao e bilateral — Tata escolhe (Conselho da Soberana avalia), mas mentorada tambem decide (auto-eleicao do caminho). Sem coercao, sem "promocao automatica".
- Selo Travessia e ativo compartilhado — quem usa o Selo (caminhos 2 e 3) recebe estrategia, infra e marca; em troca paga royalty + segue padrao de qualidade auditavel.
Quando usar
- Mentorada completou 12+ meses como Imperatriz Plena ativa (Pilar 1-6 todos saturados)
- Conselho da Soberana convocou conversa de sucessao
- Mentorada disse "terminei Travessia, e agora?"
- Tata quer mapear quem da base Plena esta pronta pra sucessao
- Mentorada esta em duvida entre os 3 caminhos
- Negociacao formal de % participacao / royalty / vesting esta no horizonte
- Sub-brand / segundo livro / manifesto publico precisam ser construidos
- Pos-decisao: planejar implementacao 90/180/365 dias
Pre-requisitos duros (a skill NAO negocia)
Antes de rodar qualquer modo, validar:
- Tempo: 12+ meses CONSECUTIVOS como Imperatriz Plena (nao basta ter atingido o titulo — precisa ter sustentado 12 meses ativa)
- Atividade: Pilar 1 (Fluxo) com gates A-Z saturados nos ultimos 90 dias
- Saude financeira: faturamento estavel ou em crescimento nos ultimos 6 meses (sem queda > 30%)
- Compliance: zero pendencia juridica/fiscal aberta, zero crise nao resolvida
- Reputacao: NPS interno (mentoradas dela, time dela) >= 8
- Disponibilidade: Tata + Conselho com agenda pra conduzir o processo (nao se faz sucessao em modo apagar incendio)
What ships with it
6 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.
- 9d ago First seen · 295 lines · 404 tokens per session scan A f0f5c6ed8bd8
sucessao-imperatriz is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 404 tokens to every session and 3,831 once invoked, about $0.0020 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
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).