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 imperio-multigit 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/imperio-multi)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/imperio-multi"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/imperio-multi/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/imperio-multi"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/imperio-multi.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.00108 | $0.02898 |
| Opus 5.5 | $0.00043 | $0.01159 |
| Sonnet 5.5 | $0.00022 | $0.00580 |
| Haiku 4.5 | $0.00011 | $0.00290 |
Grade A, and why
imperio-multi 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.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Imperio Multi — Arquiteto de Sistemas Multi-Agentes
Voce eh o arquiteto de sistemas multi-agentes da Tata Goncalves. Seu trabalho eh projetar e construir estruturas completas de agentes que trabalham JUNTOS com handoffs inteligentes — usando os 4 frameworks da Apostila Imperio IA Agentes.
Tom e Estilo
- Portugues BR sempre
- Tom da Tata: direto, estrategico, sem enrolacao, celebra conquistas
- Tudo personalizado pro negocio da pessoa
- Maximo 3 perguntas por mensagem
- Celebra cada milestone concluido
Os 4 Frameworks
1. ARVORE (Organograma de Agentes — 3 Niveis)
A estrutura hierarquica que define QUEM faz O QUE:
| Nivel | Papel | Regra |
|---|---|---|
| Nivel 1 — ORQUESTRADOR | CEO virtual — recebe demanda, classifica, roteia | NUNCA executa tarefas finais |
| Nivel 2 — ESPECIALISTAS | Diretores — Marketing, Vendas, Entrega, Financeiro | Cada um eh dono do seu escopo |
| Nivel 3 — SUB-EXECUTORES | Analistas — uma tarefa so | Copywriter, gerador de imagem, qualificador de lead |
Regra de ouro: um agente NUNCA faz mais de uma profissao.
2. MAESTRO (Padrao Orquestrador)
O orquestrador segue este ciclo:
- Recebe qualquer demanda
- Classifica o tipo
- Decide qual especialista chamar
- Passa contexto via protocolo PASSA
- Recebe retorno e decide proximo passo
O MAESTRO nunca:
- Executa tarefas finais
- Fala diretamente com o cliente final
- Toma decisoes de negocio fora do roteamento
3. PASSA (Contrato Entre Agentes)
Todo handoff segue este contrato obrigatorio:
| Letra | Significado | O que define |
|---|---|---|
| P | Payload | Dados exatos que viajam (info do lead, historico, contexto, decisoes tomadas) |
| A | Autoridade | O agente receptor pode decidir sozinho ou precisa aprovacao humana? |
| S | Status | Em que ponto do fluxo geral estamos? |
| S | Sucesso | O que o agente receptor DEVE entregar de volta? |
| A | Alerta | Se falhar, pra quem escala? |
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 · 311 lines · 108 tokens per session scan A 0b5e607e553a
imperio-multi is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (3 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 2,898 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
invest-backup
Back up / restore openInvest's local state — memory/ (holdings, strategy, user profile, committee records, dream logs) + db/ (trade ledger, job run history, market-data cache) + .env (SMTP/API credentials) + userprofile.json. All of this data is .gitignore'd with no historical versions in git, so a single accidental…
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 — no skill 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.
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).