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.
git clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/commands/gtmagents/gtm-agents/plan-community-calendar)<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/plan-community-calendar"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/plan-community-calendar/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/commands/gtmagents/gtm-agents/plan-community-calendar"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/plan-community-calendar.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.00019 | $0.00723 |
| Opus 5 | $0.00010 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
plan-community-calendar 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: plan-community-calendar
Inputs
- window – planning horizon (e.g., 8weeks, quarter).
- channels – comma-separated community surfaces (forum, Slack, Discord, events, webinar, newsletter).
- themes – optional list of focus themes or series.
- audiences – optional persona/segment filters.
- dependencies – optional notes on launches, campaigns, or partner tie-ins.
GTM Agents Pattern & Plan Checklist
Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- Pattern selection: Community calendar planning typically runs pipeline (signals → themes → programming → resources → publishing). If programming segments (e.g., events vs async drops) run in parallel, capture a diamond segment with merge gate in the plan header.
- Plan schema: Save
.claude/plans/plan-<timestamp>.jsoncapturing window, channels, task IDs, dependency graph (hosts, moderators, asset teams), error handling, and success metrics (attendance, engagement %, advocacy contributions). - Tool hooks: Reference
docs/gtm-essentials.mdstack—Serena for asset/promo diffs, Context7 for playbooks/guidelines, Sequential Thinking for governance/check-in cadence, Playwright for testing community microsites or forms if needed. - Guardrails: Default retry limit = 2 for resource shortages or tooling failures; escalation ladder = Community Lead → Marketing/CS leadership → Exec sponsor.
- Review: Run
docs/usage-guide.md#orchestration-best-practices-puerto-paritybefore execution to confirm owners, dependencies, deliverables.
Workflow
- Signal Review – pull engagement data, VOC insights, and upcoming GTM milestones.
- Theme Mapping – align themes to goals (activation, adoption, advocacy) and persona interests.
- Programming Mix – schedule events, AMAs, content drops, and spotlights with owners + formats.
- Resource Checklist – detail required assets, hosts, moderators, and promo timelines.
- Publishing Packet – output calendar plus reminders/automation hooks for each touch.
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.
- 8d ago First seen · 49 lines · 19 tokens per session scan A 47f5202a2c95
plan-community-calendar is a command published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 723 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.