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-funil-webinargit 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-funil-webinar)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/skill-funil-webinar"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-funil-webinar/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-funil-webinar"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-funil-webinar.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.00138 | $0.03508 |
| Opus 5 | $0.00069 | $0.01754 |
| Sonnet 5 | $0.00028 | $0.00702 |
| Haiku 4.5 | $0.00014 | $0.00351 |
Grade A, and why
skill-funil-webinar 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Funil de Webinar/Aula Gratuita — Mercado BR
Contexto
- Modelo: Infoprodutos, mentorias, formacoes (mercado brasileiro)
- Formato: Webinar ao vivo, aula gravada, desafio, masterclass, imersao
- Plataformas de entrega: YouTube Live, Zoom, Hotmart, EAD
Processo
1. Definicao do Funil
Perguntar ao usuario:
- Nome do produto/oferta (o que vai vender no final)
- Preco do produto
- Formato: webinar unico, serie de 3, desafio 5 dias, masterclass
- Data do evento (se ao vivo)
- Tema da aula gratuita
- Beneficio #1 que o participante vai sair com
- Oferta de entrada (se houver — tripwire, ingresso, etc)
2. Estrutura Completa do Funil
FASE 1 — CAPTACAO (7-14 dias antes)
├── Ads (Meta + Google) → Landing Page Inscricao
├── Conteudo organico (Reels, Stories, Posts)
├── Lista de email → Convite
└── WhatsApp → Convite pessoal
FASE 2 — AQUECIMENTO (3-7 dias antes)
├── Email 1: Confirmacao + o que esperar
├── Email 2: Conteudo preparatorio (mini-insight)
├── Email 3: Lembrete 24h
├── WhatsApp: Lembrete 1h antes
├── Stories: Countdown + bastidores
└── Retargeting: Inscritos que nao abriram emails
FASE 3 — EVENTO (Dia do webinar)
├── Email: "Comecou! Entre agora"
├── WhatsApp: Link direto
├── Webinar ao vivo (60-90 min)
│ ├── Bloco 1: Hook + Promessa (5 min)
│ ├── Bloco 2: Historia/Autoridade (10 min)
│ ├── Bloco 3: Conteudo de Valor (25-35 min)
│ ├── Bloco 4: Transicao para Oferta (5 min)
│ ├── Bloco 5: Apresentacao da Oferta (15 min)
│ └── Bloco 6: Q&A + Urgencia (10-20 min)
└── Chat ao vivo com equipe (links, duvidas)
FASE 4 — POS-EVENTO (7 dias)
├── Email 1: Replay + Oferta (imediatamente)
├── Email 2: Depoimento + Bonus (Dia 1)
├── Email 3: Objecao #1 respondida (Dia 2)
├── Email 4: Objecao #2 respondida (Dia 3)
├── Email 5: Escassez — bonus expira (Dia 5)
├── Email 6: Ultimo dia (Dia 7)
├── Email 7: Carrinho fechando (Dia 7, 23h)
├── WhatsApp: Follow-up personalizado
├── Retargeting: Replay viewers + PV sem compra
└── Stories: Depoimentos, countdown, bastidores
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 · 453 lines · 138 tokens per session scan A 52a332487c17
skill-funil-webinar is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 138 tokens to every session and 3,508 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.