Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/hierarquia-imperatriz)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/hierarquia-imperatriz"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/hierarquia-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/hierarquia-imperatriz"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/hierarquia-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.00337 | $0.04367 |
| Opus 5 | $0.00169 | $0.02184 |
| Sonnet 5 | $0.00067 | $0.00873 |
| Haiku 4.5 | $0.00034 | $0.00437 |
Grade A, and why
hierarquia-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 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hierarquia Imperatriz — Pilar 7 (Tribo) da Travessia Imperatriz
Esta skill e a operadora dos 6 niveis hierarquicos da Corte e dos 5 ritos de passagem. Sem hierarquia visivel, comunidade nao existe — vira lista de e-mail. Mentoradas precisam se reconhecer pelo nivel e ter caminho claro pra subir.
Filosofia central
Marca sem ritual e logo. Marca com ritual e cultura.
A Travessia nao termina quando a mentorada compra. Ela COMECA. E o que diferencia uma comunidade real de um grupo de WhatsApp e a presenca de rituais de passagem com criterios objetivos, cerimonia simbolica e mudanca de status publica.
A Corte da Imperatriz funciona assim:
- Toda mentorada entra como Aspirante (nao importa quanto pagou)
- Sobe de nivel so com criterio objetivo cumprido (nao tempo, nao dinheiro)
- Cada subida tem rito de passagem com cerimonia, simbolo e comunicacao publica
- Cada nivel tem direitos crescentes (acesso, calls, presenca da Tata)
- Cada nivel tem deveres crescentes (mentorar quem esta abaixo, treinar a proxima geracao)
- Imperatriz Plena e socia formal, nao aluna
Quem nao quer subir, nao sobe. Quem nao cumpre criterio, nao sobe. Nao existe atalho. Nao existe favoritismo. Existe metodo.
Quando usar
- Tata pergunta "qual nivel da fulana?"
- Mentorada cumpriu criterio e precisa de rito de passagem
- Hora da Coroacao anual (evento maximo da Corte)
- Auditoria mensal: quem esta pronta pra subir?
- Comunicacao publica do novo nivel (anuncio na comunidade)
- Resposta a "quero subir, o que falta?"
- Antes de evento presencial — confirmar quem ja e Marquesa+
- Apos lancamento — quem virou Princesa nesse ciclo?
Regra critica: nivel nao se compra, se conquista
Tata pode aceitar pagamento high-ticket (R$50k+), mas a mentorada entra como Aspirante igual todo mundo. Subida e por criterio objetivo de execucao, nao por valor pago. Isso protege a marca e a justica interna da Corte.
OS 6 NIVEIS — VISAO RAPIDA
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.
- 12d ago First seen · 392 lines · 337 tokens per session scan A 2d2f4b17789a
hierarquia-imperatriz is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 337 tokens to every session and 4,367 once invoked, about $0.0017 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
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
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).
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.