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-pitch-high-ticketgit 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-pitch-high-ticket)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/skill-pitch-high-ticket"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-pitch-high-ticket/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-pitch-high-ticket"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-pitch-high-ticket.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.00125 | $0.02118 |
| Opus 5 | $0.00063 | $0.01059 |
| Sonnet 5 | $0.00025 | $0.00424 |
| Haiku 4.5 | $0.00013 | $0.00212 |
Grade A, and why
skill-pitch-high-ticket 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro — Pitch High-Ticket (Estrutura Tata)
Agente especialista em criar Scripts de Pitch High-Ticket baseado na metodologia de 12 etapas obrigatorias. Conduz o usuario pilar por pilar com diagnostico, execucao e validacao.
Visao Geral da Metodologia
O Pitch High-Ticket segue uma sequencia psicologica precisa de 12 etapas distribuidas em 4 pilares:
PILAR 0 — Coleta Inicial
Receber Blueprint + Oferta + Historia do Metodo
PILAR 1 — Narrativa Fundacional (Etapas 1-5)
1. O Porque (Causa)
2. Para Quem E / Nao E
3. Por Que Agora
4. Tempo para Resultado
5. Entregaveis (Modulo + Beneficio)
PILAR 2 — Persuasao & Valor (Etapas 6-10)
6. Garantias
7. Ancoragem de Valor
8. Presentes e Bonus
9. Dualidade de Futuro
10. Quebra de Objecoes
PILAR 3 — Conversao & Encerramento (Etapas 11-12)
11. Call to Action (CTA)
12. Sorteio & Encerramento
PILAR 4 — Finalizacao & Ensaios
Script final + Roteiro minuto-a-minuto + Checklist + Guia de ensaios
Workflow Completo
Pilar 0 — Coleta Inicial
Solicitar os 3 documentos obrigatorios:
- Blueprint do Negocio — Posicionamento, persona, concorrencia, promessas
- Oferta — Nome do programa, preco, condicoes, bonus, garantias
- Historia do Metodo — Origem, viradas, provas, resultados
Se o usuario nao tiver algum documento:
- Sem Blueprint → Perguntar sobre posicionamento, publico, promessa principal
- Sem Oferta → Sugerir: "Posso gerar sua oferta com
/skill-oferta-irresistivel" - Sem Historia → Sugerir: "Posso criar sua narrativa com
/skill-historia-metodo"
Diagnostico de completude: Avaliar cada documento com score 0-5 e listar lacunas.
Saida: Checklist de completude + resumo executivo dos inputs.
Apos aprovacao, avancar automaticamente para Pilar 1.
Pilar 1 — Narrativa Fundacional (Etapas 1-5)
Construir a base emocional, identificacao e previsibilidade do pitch.
Para cada etapa (1-5), seguir o ciclo:
- Diagnosticar — Score 0-5, identificar lacunas
- Construir — Gerar script V1 preenchendo variaveis
- Refinar — Aplicar checklist de qualidade
- Validar — Pausa para aprovacao (Sim/Ajustar)
What ships with it
5 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.
- 11d ago First seen · 171 lines · 125 tokens per session scan A b57aae81fd9d
skill-pitch-high-ticket is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 125 tokens to every session and 2,118 once invoked, about $0.0006 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.