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/calendario-imperatriz)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/calendario-imperatriz"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/calendario-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/calendario-imperatriz"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/calendario-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.00335 | $0.05668 |
| Opus 5 | $0.00168 | $0.02834 |
| Sonnet 5 | $0.00067 | $0.01134 |
| Haiku 4.5 | $0.00034 | $0.00567 |
Grade A, and why
calendario-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 — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendário Imperatriz — Porta N (Narrativa) da Travessia
Motor de calendário editorial UNIFICADO que cruza 6 canais sem canibalização. Aplica a lógica 1 ideia central por semana × 5 adaptações por canal pra entregar 30 peças/mês com coerência narrativa, voz de marca preservada e zero repetição preguiçosa.
Filosofia central
Não posta tudo em todo lugar. Adapta uma ideia única em 5 formatos pra 5 canais — e espaça 2-3 dias entre cada peça.
Canibalização acontece quando o mesmo conteúdo aparece copy-paste em vários canais no mesmo dia. O resultado: stories e feed se anulam, email vira eco do post, LinkedIn vira screenshot do Instagram, ninguém engaja em lugar nenhum. A solução é reaproveitamento ESTRUTURADO — mesma ideia, formato diferente, tom calibrado por canal, espaçamento temporal.
Quando usar
- Mentoranda quer planejar 30 dias de conteúdo de uma vez
- Mentoranda já tem 1 ideia/aula/insight e quer transformar em pacote multicanal
- Mentoranda está perdida no "o que postar hoje?" semanalmente
- Tata quer auditar calendário de mentoranda e identificar canibalização
- Cruzamento com lançamento atual (Porta L) ou sazonalidade (Black Friday, Páscoa)
- Antes de despachar pras skills filhas (carrossel, stories, LinkedIn, email)
Os 6 canais oficiais da Imperatriz
| # | Canal | Formato dominante | Frequência ideal | Tom |
|---|---|---|---|---|
| 1 | Instagram Carrossel (feed) | 7 slides 4:5 (1080×1350) | 2-3×/semana | Educativo + autoridade |
| 2 | Instagram Stories | 9:16 (1080×1920) | 4-8×/dia | Bastidor + Q&A + enquete |
| 3 | Instagram Reels | 9:16 vídeo curto (15-60s) | 1-2×/semana | Viral + emoção + hook |
| 4 | LinkedIn (post longo) | Texto 1300-2000 caracteres | 2×/semana | Pensamento de longo prazo |
| 5 | Email (newsletter) | 400-800 palavras | 1-2×/semana | Conversa íntima |
| 6 | WhatsApp Status | 9:16 estático ou 5-15s vídeo | 1-3×/dia | Bastidor cru + CTA direto |
Lógica não-canibalização (4 regras duras)
What ships with it
8 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 · 494 lines · 335 tokens per session scan A ffdb4c494870
calendario-imperatriz is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 335 tokens to every session and 5,668 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.