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 skill-escala-adsgit 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/skill-escala-ads)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/skill-escala-ads"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-escala-ads/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/skill-escala-ads"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-escala-ads.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.00153 | $0.03123 |
| Opus 5 | $0.00077 | $0.01562 |
| Sonnet 5 | $0.00031 | $0.00625 |
| Haiku 4.5 | $0.00015 | $0.00312 |
Grade A, and why
skill-escala-ads 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 11d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sistema de Escala e Otimizacao de Ads
Contexto
- Foco: Meta Ads + Google Ads
- Mercado: Infoprodutos, mentorias (Brasil)
- Moeda: BRL
Processo
1. Diagnostico
Perguntar ao usuario:
- Campanha/plataforma em questao
- Metricas atuais (CPA, ROAS, CTR, frequencia, gasto)
- Meta de CPA/ROAS
- Budget atual
- Ha quanto tempo esta rodando
- Fase: learning, otimizado, escala
2. Decision Trees
Arvore Principal: O que Fazer com Esta Campanha?
PERGUNTA 1: A campanha tem conversoes?
│
├── NAO → PERGUNTA 2: Gastou mais que 3x CPA alvo?
│ ├── SIM → ❌ KILL (Pausar Imediatamente)
│ │ → Aplicar Kill Rule Protocol (ver secao 4)
│ └── NAO → ⏳ ESPERAR
│ → Campanha pode estar em Learning Phase
│ → Esperar ate gastar 3x CPA antes de decidir
│
└── SIM → PERGUNTA 3: CPA atual vs CPA alvo?
│
├── CPA < Alvo (-10% ou mais) → PERGUNTA 4: Fase de aprendizado?
│ ├── SIM (em Learning) → ⏳ ESPERAR aprendizado terminar
│ └── NAO (saiu do Learning) → ✅ ESCALAR
│ → Aplicar Escala Protocol (ver secao 3)
│
├── CPA = Alvo (±10%) → 🔧 MANTER e OTIMIZAR
│ → Testar novos criativos
│ → Testar novos publicos
│ → NAO mexer no budget
│
└── CPA > Alvo (+10% ou mais) → PERGUNTA 5: Ha quanto tempo?
├── < 7 dias → ⏳ ESPERAR (pode ser flutuacao)
├── 7-14 dias → 🔧 OTIMIZAR (ver secao 5)
└── > 14 dias → ❌ KILL ou REFORMULAR
Arvore de Criativos: Manter ou Trocar?
PERGUNTA: O criativo esta performando bem?
│
├── CTR > meta E CPA < alvo → ✅ MANTER
│ → Monitorar frequencia
│ → Se frequencia > 4 → Expandir audiencia
│
├── CTR caiu > 20% em 14 dias → ⚠️ FADIGA
│ → Pausar criativo
│ → Substituir por nova versao
│ → Manter conceito mas mudar execucao (novo hook, novo visual)
│
├── CTR OK mas CPA alto → 🔧 PROBLEMA NO FUNIL
│ → Landing page pode ser o gargalo
│ → Testar nova LP antes de trocar criativo
│
└── CTR baixo desde inicio (< 0.5%) → ❌ KILL
→ Criativo nao ressoou
→ Testar conceito totalmente diferente
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.
- 11d ago First seen · 313 lines · 153 tokens per session scan A f730f968af37
skill-escala-ads is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 153 tokens to every session and 3,123 once invoked, about $0.0008 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.