planejar-uma-campanha

planejar-uma-campanha is a skill for Claude Code, Codex from gethouston/houston. It costs 97 tokens per session (3,081 once invoked), scanned A, original, MIT.

A campaign planning skill that turns your positioning and customer information into a detailed plan for advertising, product launches, automated email sequences, welcome emails, retention emails, or feature announcements.

In plain words
What is it for?
Use it to specify paid campaigns, launch timelines, lifecycle emails, five-part welcome series, churn-saving messages, or coordinated email and in-app announcements.
Why use it?
It removes the need to work out the audience, schedule, messages, and success measures from scratch for each campaign.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to specify paid campaigns, launch timelines, lifecycle emails, five-part welcome series, churn-saving messages, or coordinated email and in-app announcements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/planejar-uma-campanha
Install

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.

Any agent
npx skills add gethouston/houston --skill planejar-uma-campanha
Clone the repo
git clone --depth 1 https://github.com/gethouston/houston

Made for: Claude Code, Codex.

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.

agentmods badge for planejar-uma-campanha

README.md
[![agentmods](https://agentmods.dev/badge/skills/gethouston/houston/planejar-uma-campanha/github.svg)](https://agentmods.dev/skills/gethouston/houston/planejar-uma-campanha)
Your own site
<a href="https://agentmods.dev/skills/gethouston/houston/planejar-uma-campanha"><img src="https://agentmods.dev/badge/skills/gethouston/houston/planejar-uma-campanha/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.

agentmods 80×15 button for planejar-uma-campanha

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/planejar-uma-campanha"><img src="https://agentmods.dev/badge/skills/gethouston/houston/planejar-uma-campanha.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00097 $0.03081
Opus 5 $0.00048 $0.01541
Sonnet 5 $0.00019 $0.00616
Haiku 4.5 $0.00010 $0.00308

Measured 9d ago against content hash 9efdfe7496b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

planejar-uma-campanha 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.

store/agents-i18n/pt/marketing/.agents/skills/planejar-uma-campanha/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Planejar uma Campanha

Uma skill, toda especificação de campanha. O parâmetro type escolhe o formato; posicionamento, voz, cliente ideal, "só rascunhos, sem táticas de culpa" são compartilhados.

Parâmetro: type

  • paid - público + palavras-chave / posicionamento de anúncio + estrutura de grupo de anúncios + orçamento + requisito de landing page + KPIs.
  • launch - plano de 2 semanas sequenciado do Dia -7 ao Dia 0 ao Dia +7, cada tarefa marcada com a skill dentro DESTE agente que a executa.
  • lifecycle-drip - sequência disparada por evento com gatilho + evento-meta + regras de frequência + ramificação por ação do usuário + e-mails redigidos.
  • welcome - série de 5 e-mails para novos cadastros (Dia 0 / 1 / 3 / 7 / 14 padrão, pode sobrescrever qualquer cadência).
  • churn-save - e-mail de retenção oferecendo UMA opção genuína (pausa / downgrade / atendimento consultivo / reembolso). Sem táticas de culpa.
  • announcement - copy de e-mail + copy correspondente no app (banner + modal + aviso de estado vazio), tudo ligado ao mesmo CTA principal.

O usuário nomeia o tipo em português simples, eu infiro. Se ambíguo, faço UMA pergunta nomeando as 6 opções.

Quando usar

  • Explícito: "planejar uma campanha paga em {channel}", "planejar o lançamento de {feature}", "desenhar um drip para {segment}", "redigir uma série de boas-vindas", "e-mail de retenção para {account}", "redigir o anúncio de {feature}".
  • Implícito: chamado depois de audit-a-surface (landing-page / site-seo) quando o fundador está pronto para investir orçamento por trás de uma página já corrigida.

Conexões que preciso

Eu executo trabalho externo através do Composio. Antes desta skill rodar, verifico se as categorias abaixo estão conectadas. Se faltar, eu nomeio a categoria, peço para você conectar na aba Integrações e paro.

  • Plataforma de e-mail (Customer.io, Loops, Mailchimp, Kit, etc.) - redigir e-mails de drip / boas-vindas / retenção / anúncio no seu remetente. Obrigatório para lifecycle-drip, welcome, churn-save, announcement.
  • Plataformas de anúncio (Google Ads, Meta Ads, LinkedIn Ads) - puxar conta, público e formato de palavras-chave para o briefing encaixar na sua conta real. Obrigatório para paid (o canal que você está planejando).
  • CRM (HubSpot, Salesforce, Attio) - segmentar públicos e puxar gatilhos comportamentais. Opcional, mas melhora a precisão da segmentação.
  • Cobrança (Stripe) - sinalizar sinais de downgrade e cancelamento para churn-save. Obrigatório para churn-save.

Read the full file on GitHub · 85 lines

Changes

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.

  1. 9d ago First seen · 85 lines · 97 tokens per session scan A 9efdfe7496b6

Subscribe to this mod's changes

planejar-uma-campanha is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 3,081 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

magazine-web-ppt

For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.

nexu-io/open-design · 67 tokens

html-ppt-zhangzara-coral

OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.

nexu-io/open-design · 55 tokens

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad…

coreyhaines31/marketingskills · 175 tokens

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives…

coreyhaines31/marketingskills · 220 tokens

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership…

coreyhaines31/marketingskills · 92 tokens

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this,"…

coreyhaines31/marketingskills · 152 tokens