coordinate-channels

coordinate-channels is a command for Claude Code from gtmagents/gtm-agents. It costs 16 tokens per session (351 once invoked), scanned A, original, Apache-2.0.

A command for aligning schedules, messages, owners, requirements, approvals, and quality checks across campaign channels.

In plain words
What is it for?
It helps generate channel calendars, channel-specific checklists, risk logs, and reporting requirements for a defined campaign period.
Why use it?
It gives cross-channel teams a shared calendar and makes dependencies and blockers visible before launch.

Command for Claude Code

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

Good fit It helps generate channel calendars, channel-specific checklists, risk logs, and reporting requirements for a defined campaign period.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/coordinate-channels"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/coordinate-channels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 351 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.00016 $0.00351
Opus 5 $0.00008 $0.00176
Sonnet 5 $0.00003 $0.00070
Haiku 4.5 $0.00002 $0.00035

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

Security

Grade A, and why

coordinate-channels 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/coordinate-channels.md · 42 lines

What it actually says

Coordinate Channels Command

Purpose

Provide a unified execution plan for cross-channel campaigns, detailing cadences, owners, specs, and QA checkpoints.

Syntax

/campaign-orchestration:coordinate-channels \
  --campaign "<name>" \
  --channels "email,social,paid,events" \
  --start "2025-01-10" \
  --end "2025-02-28"

Parameters

  • --campaign: Campaign name or ID.
  • --channels: Comma-delimited list of channels to orchestrate.
  • --start / --end: Run dates for calendar generation.
  • --budget: Optional channel budget map (JSON or CSV).
  • --offers: Asset bundle or offer IDs to align messaging.
  • --tracking: UTM/taxonomy style guide reference.

Output Package

  • Master channel calendar (table + ICS export) with send dates, owners, statuses.
  • Channel-specific checklists (assets required, approvals, QA steps, trafficking notes).
  • Risk log (dependencies, blockers, mitigations).
  • Reporting expectations (metrics per channel, refresh cadence).

Best Practices

  • Sequence channels for storytelling (teaser -> announcement -> nurture).
  • Lock copy deadlines at least 5 business days before launch.
  • Share QA sign-off path (creative, legal, ops) to avoid delays.
  • Maintain single source of truth for UTMs and tracking scripts.

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 · 42 lines · 16 tokens per session scan A a30f37c389ae

Subscribe to this mod's changes

coordinate-channels is a command published in the GitHub repository gtmagents/gtm-agents (398 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 351 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.