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/criativos-dor-beneficio)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/criativos-dor-beneficio"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/criativos-dor-beneficio/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-dor-beneficio"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/criativos-dor-beneficio.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.00061 | $0.03312 |
| Opus 5 | $0.00030 | $0.01656 |
| Sonnet 5 | $0.00012 | $0.00662 |
| Haiku 4.5 | $0.00006 | $0.00331 |
Grade A, and why
criativos-dor-beneficio 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Criativos Dor → Beneficio (Meta Ads)
Gera criativos de anuncio no formato Dor → Beneficio com 2 formatos independentes:
- Story (1080x1920): Foto do expert clonada por IA (Gemini) no topo + copy embaixo
- Feed (1080x1350): Layout texto puro (sem foto) — header escuro + copy que CABE inteira
Quando usar
- Usuario pede criativo de anuncio com dores e beneficios
- Pede anuncio estilo "Copy Experience", "antes/depois", "PAS"
- Quer gerar ads com foto clonada do expert
- Menciona "dor e beneficio", "pain points", "ad creative"
Stack tecnica
- Projeto:
~/criativos-agent/ - Gerador:
node generate-dor-beneficio.mjs --input data.json --output <dir> - Renderer Story:
lib/dor-beneficio-render.mjs(Canvas + Sharp — foto + overlay) - Renderer Feed:
lib/dor-beneficio-feed-render.mjs(Canvas — texto puro, sem foto) - Fotos IA: Gemini 2.5 Flash Image com identity preservation (inlineData)
- Fotos de referencia:
~/criativos-agent/assets/expert/foto1.png,foto2.png,foto3.png - API Key Gemini: Em
~/criativos-agent/.env(GEMINI_API_KEY) - Fontes: Inter (Regular, Medium, SemiBold, Bold) em
~/criativos-agent/fonts/
Formatos de output
Story (1080x1920) — COM foto IA
┌──────────────────────────────┐
│ FOTO DO EXPERT │ ← 40% topo (768px) — foto 16:9
│ (gerada por Gemini) │ fitted na zona, SEM crop no rosto
│ │
│ IMERSÃO │ ← overlay: logo + badge sobre a foto
│ Negócio em 48H │ fade gradiente foto → fundo bege
│ [21 E 22 DE JUNHO] │
├──────────────────────────────┤
│ ❌ Dor 1 │ ← caixas bordô, icone X, bold
│ ❌ Dor 2 │
│ ❌ Dor 3 │
├──────────────────────────────┤
│ Frase de transição │ ← texto escuro centralizado
├──────────────────────────────┤
│ ✅ Benefício 1 │ ← caixas verde-escuro, check, bold
│ ✅ Benefício 2 │
│ ✅ Benefício 3 │
├──────────────────────────────┤
│ CTA + Botão │
└──────────────────────────────┘
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 · 268 lines · 61 tokens per session scan A e8a53f2da2cb
criativos-dor-beneficio is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 3,312 once invoked, about $0.0003 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.