launch-campaign

launch-campaign is a command for Claude Code from gtmagents/gtm-agents. It costs 19 tokens per session (2,467 once invoked), scanned A, original, Apache-2.0.

A command that coordinates specialized agents to plan and run a marketing campaign across strategy, creative work, distribution, and analytics.

In plain words
What is it for?
It helps organize campaign strategy, audiences, content, design, copy, channel distribution, and performance analysis.
Why use it?
It brings the major campaign workstreams into one coordinated process from planning to launch and review.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit It helps organize campaign strategy, audiences, content, design, copy, channel distribution, and performance analysis.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/gtmagents/gtm-agents/launch-campaign
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.

Clone the repo
git clone --depth 1 https://github.com/gtmagents/gtm-agents

Made for: Claude Code.

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 launch-campaign

README.md
[![agentmods](https://agentmods.dev/badge/commands/gtmagents/gtm-agents/launch-campaign/github.svg)](https://agentmods.dev/commands/gtmagents/gtm-agents/launch-campaign)
Your own site
<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/launch-campaign"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/launch-campaign/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 launch-campaign

Your own site · 80×15
<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/launch-campaign"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/launch-campaign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,467 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.
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.00019 $0.02467
Opus 5 $0.00010 $0.01234
Sonnet 5 $0.00004 $0.00493
Haiku 4.5 $0.00002 $0.00247

Measured 7d ago against content hash 8e4dc5f13eee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

launch-campaign 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 7d 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.

plugins/campaign-orchestration/commands/launch-campaign.md · 347 lines

How it starts

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

Campaign Orchestration Workflow

Multi-agent orchestration for end-to-end marketing campaign execution, coordinating strategy, creative, distribution, and analytics across multiple channels.

Command Syntax

/campaign-orchestration:launch-campaign "<campaign_name>" --type <type> --budget <amount> --timeline <weeks>

Orchestration Overview

This orchestrator coordinates 8+ specialized agents to execute comprehensive marketing campaigns:

┌────────────────────────────────────────┐
│        Campaign Orchestrator           │
│         (Master Coordinator)           │
└────────────────┬───────────────────────┘
                 │
    ┌────────────┴────────────┐
    │                         │
┌───▼──────┐          ┌───────▼──────┐
│Strategy  │          │ Creative     │
│Agents    │          │ Agents       │
├──────────┤          ├──────────────┤
│Campaign  │          │Content       │
│Strategist│          │Creator       │
│Audience  │          │Designer      │
│Analyst   │          │Copy Writer   │
└──────────┘          └──────────────┘
    │                         │
    └────────────┬────────────┘
                 │
    ┌────────────┴────────────┐
    │                         │
┌───▼──────┐          ┌───────▼──────┐
│Channel   │          │ Analytics    │
│Agents    │          │ Agents       │
├──────────┤          ├──────────────┤
│Email     │          │Data Analyst  │
│Social    │          │Attribution   │
│Paid Media│          │ROI Calculator│
│SEO       │          │Dashboard     │
└──────────┘          └──────────────┘

GTM Agents Pattern & Plan Checklist

Based on GTM Agents's orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325.

  • Pattern Selection: default to pipeline (Strategy → Creative → Channels → Optimization). Switch to diamond/fan-out when creative/analytics work can parallelize; note pattern choice in the plan header.
  • Plan Schema: every /campaign-orchestration run must emit a JSON plan saved under .claude/plans/plan-<timestamp>.json with objective, complexity, stages, task IDs, parallelization block, context-passing notes, error handling, and success criteria.
  • Tool Hooks: reference docs/gtm-essentials.md tools inside plan steps (Serena for code/landing-page patches, Context7 for doc lookups, Sequential Thinking for retros, Playwright for QA checkpoints).
  • Guardrails & Escalation: define retry strategy (immediate vs modified), max retries (default 2), and escalation path (Campaign Strategist → RevOps lead) for failures.
  • Review Flow: before execution, run the checklist from docs/usage-guide.md#orchestration-best-practices-puerto-parity (agent availability, dependency validation, deliverables alignment).

Read the full file on GitHub · 347 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. 7d ago First seen · 347 lines · 19 tokens per session scan A 8e4dc5f13eee

Subscribe to this mod's changes

launch-campaign is a command published in the GitHub repository gtmagents/gtm-agents (398 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,467 once invoked, about $0.0001 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.