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 criativos-mentoradosgit 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/criativos-mentorados)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/criativos-mentorados"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/criativos-mentorados/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/criativos-mentorados"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/criativos-mentorados.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.00137 | $0.01916 |
| Opus 5 | $0.00068 | $0.00958 |
| Sonnet 5 | $0.00027 | $0.00383 |
| Haiku 4.5 | $0.00014 | $0.00192 |
Grade A, and why
criativos-mentorados-setup 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Criativos — Configuracao do Mentorado
Este onboarding coleta e salva as informacoes do mentorado UMA UNICA VEZ para que todas as skills de criativos funcionem com a identidade e chave dele.
O que e coletado
- Fotos de referencia (1 a 3 fotos) — usadas pelo Gemini para clonar a identidade
- Chave Gemini API — para gerar as fotos com IA
- Descricao fisica — para os prompts de geracao de foto
- Nome — para overlay nos criativos
- Instagram — para overlay nos criativos (opcional)
Onde salva
~/.criativos-mentorados/
config.json — todas as configs
assets/
foto1.png — foto de referencia 1
foto2.png — foto de referencia 2 (opcional)
foto3.png — foto de referencia 3 (opcional)
Processo de Onboarding (SEGUIR EXATAMENTE)
Passo 1: Verificar se ja existe config
cat ~/.criativos-mentorados/config.json 2>/dev/null
Se existir, mostrar ao mentorado:
- "Voce ja tem um perfil configurado! Aqui estao seus dados:"
- Mostrar nome, instagram, quantas fotos, descricao
- Perguntar: "Quer atualizar algo ou esta tudo certo?"
- Se quiser atualizar, prosseguir com os passos abaixo (so os campos que quer mudar)
Se NAO existir, comecar onboarding completo:
Passo 2: Criar diretorio
mkdir -p ~/.criativos-mentorados/assets
Passo 3: Coletar FOTOS de referencia
Dizer ao mentorado:
Suas fotos de referencia
Preciso de 1 a 3 fotos suas para a IA clonar sua identidade nos criativos.
Regras das fotos:
- Rosto bem visivel, boa iluminacao
- De preferencia fotos diferentes (angulos, roupas, cenarios)
- Podem ser selfies ou fotos profissionais
- Formato: PNG ou JPG
- Minimo 1 foto, ideal 3
Como enviar:
Arraste as fotos aqui no chat, ou me diga o caminho completo dos arquivos.
Exemplo: ~/Downloads/minha-foto.png
Quando o mentorado fornecer as fotos:
- Copiar cada foto para
~/.criativos-mentorados/assets/foto1.png,foto2.png,foto3.png - Usar
cp(NUNCA mover, sempre copiar) - Verificar que os arquivos existem apos copiar
What ships with it
4 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 · 225 lines · 137 tokens per session scan A 24fd5f6c7ad8
criativos-mentorados-setup is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 137 tokens to every session and 1,916 once invoked, about $0.0007 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.