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/content-pipeline)<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/content-pipeline"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/content-pipeline/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/content-pipeline"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/content-pipeline.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.00021 | $0.00413 |
| Opus 5 | $0.00010 | $0.00206 |
| Sonnet 5 | $0.00004 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
content-pipeline 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.
What it actually says
Content Pipeline Command
Coordinate strategy, production, and distribution for multi-channel content programs aligned to business goals.
Command Syntax
/content-marketing:content-pipeline "<program_name>" --duration <timeframe> --frequency <cadence>
Parameters
program_name(positional): Theme or campaign name--duration: Calendar window (e.g., 6weeks, 3months)--frequency: Publishing cadence (weekly|biweekly|monthly)--channels: Comma-delimited list of channels (blog,email,social,webinar)--personas: Target personas for tailoring content--assets: Required asset types (pillar, blog, social, video)
Workflow Phases
- Strategy Alignment – map program goals, KPIs, personas, and messaging pillars.
- Editorial Planning – build calendar with pillar assets plus derivative formats per channel.
- Production Sprinting – assign owners, outline briefs, define review/QA gates.
- Distribution & Promotion – schedule owned, earned, and paid pushes with UTMs.
- Performance Review – capture metrics, insights, and optimization backlog.
Output Package
- Editorial calendar (table/json)
- Asset brief templates with key messages, CTA, SEO targets
- Channel distribution checklist per asset
- Measurement plan with KPIs per stage (awareness, consideration, decision)
Best Practices
- Anchor each pillar asset to a buyer-journey stage and repurpose across channels.
- Pair every asset with a distribution plan before production starts.
- Bake in approvals and localization windows to avoid publishing slips.
- Track performance weekly; adapt upcoming topics based on leading indicators.
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 · 48 lines · 21 tokens per session scan A 029899252b6e
content-pipeline is a command published in the GitHub repository gtmagents/gtm-agents (398 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 413 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.