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-sequencia-vendasgit 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-sequencia-vendas)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/skill-sequencia-vendas"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-sequencia-vendas/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-sequencia-vendas"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-sequencia-vendas.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.00146 | $0.03046 |
| Opus 5 | $0.00073 | $0.01523 |
| Sonnet 5 | $0.00029 | $0.00609 |
| Haiku 4.5 | $0.00015 | $0.00305 |
Grade A, and why
skill-sequencia-vendas 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 9d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequencia de Vendas Multi-Canal — Mercado BR
Contexto
- Canais: Email + WhatsApp + Retargeting Ads + SMS (opcional)
- Mercado: Brasil — infoprodutos, mentorias, formacoes
- Ferramentas comuns: ActiveCampaign, RD Station, Leadlovers, Hotmart, Eduzz
Processo
1. Definicao da Sequencia
Perguntar ao usuario:
- Tipo: lancamento, perpetuo, carrinho aberto, pos-webinar, onboarding
- Produto/oferta (nome, preco, beneficio)
- Duracao da sequencia (3, 7, 14, 21 dias)
- Canais disponiveis (email, WhatsApp, SMS, retargeting)
- Gatilho de entrada (inscricao, download, webinar, visita PV)
2. Arquiteturas de Sequencia
Tipo 1: Pos-Webinar (7 dias) — MAIS COMUM
GATILHO: Participou do webinar OU assistiu replay
DIA 0 (Imediato)
├── Email: Replay + Oferta + Bonus
├── WhatsApp: "Gostou da aula? Inscricoes abertas"
└── Retargeting: Video oferta para viewers do webinar
DIA 1
├── Email: Depoimento forte + Bonus
├── WhatsApp: Depoimento (audio ou texto)
└── Retargeting: Carrossel depoimentos
DIA 2
├── Email: Quebra de Objecao #1 ("sera que funciona?")
└── Retargeting: Video quebrando objecao
DIA 3
├── Email: Conteudo de valor + menção sutil da oferta
├── WhatsApp: Dica rapida + "ja viu a oferta?"
└── Retargeting: Imagem oferta + bonus
DIA 5
├── Email: ⚠️ Bonus expirando em 48h
├── WhatsApp: "Os bonus vencem em 48h"
└── Retargeting: Urgencia — countdown
DIA 6
├── Email: Ultimo dia + depoimento final
└── WhatsApp: "Amanha encerra"
DIA 7 (Manha)
├── Email: ULTIMO DIA
├── WhatsApp: "Hoje e o ultimo dia"
└── Retargeting: "Encerra hoje"
DIA 7 (23h)
├── Email: "Encerra a meia-noite"
├── WhatsApp: "Ultima chance"
└── Retargeting: Pausa apos meia-noite
Tipo 2: Carrinho Aberto (5 dias)
GATILHO: Visitou pagina de vendas OU iniciou checkout
HORA 1
├── Email: "Percebi que voce visitou..."
└── WhatsApp: "Vi que voce estava olhando [produto]"
DIA 1
├── Email: Depoimento + FAQ
└── Retargeting: Depoimento video
DIA 2
├── Email: Objecao principal respondida
└── WhatsApp: Audio da mentora respondendo duvida
DIA 3
├── Email: Bonus extra por tempo limitado
└── Retargeting: Bonus + countdown
DIA 5
├── Email: "Ultima oportunidade — encerra hoje"
├── WhatsApp: "Ultimo dia [produto] com condicao especial"
└── Retargeting: Encerra hoje
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.
- 9d ago First seen · 350 lines · 146 tokens per session scan A c49b01a90dfb
skill-sequencia-vendas is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 146 tokens to every session and 3,046 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-09-03.
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.