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/distribute-assets)<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/distribute-assets"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/distribute-assets/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/distribute-assets"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/distribute-assets.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.00020 | $0.00696 |
| Opus 5 | $0.00010 | $0.00348 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
distribute-assets 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: distribute-assets
Inputs
- pillar – content pillar or campaign name.
- channels – comma-separated list (blog, CMS, email, social, paid, partner, enablement).
- partners – optional partner/community co-marketing list.
- utm – optional base UTM template.
- boosts – optional paid boost budget or parameters.
GTM Agents Pattern & Plan Checklist
Mirrors GTM Agents orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325.
- Pattern selection: Default to pipeline (mapping → prep → amplification → measurement → feedback). If channel prep + amplification can run in parallel, log a diamond with merge gate.
- Plan schema: Save
.claude/plans/plan-<timestamp>.jsoncapturing objective, stages, task IDs, channel groupings, context passing (UTMs, assets), guardrails, and success metrics (engagement, pipeline, partner reach). - Tool hooks: Reference
docs/gtm-essentials.mdstack (Serena for CMS/pixel patches, Context7 for platform docs, Sequential Thinking for retro cadence, Playwright for landing/social QA). - Guardrails: Set retry limit (default 2) for failed publishes; escalation ladder = Distribution Lead → Editorial Director → Marketing Director.
- Review: Use
docs/usage-guide.md#orchestration-best-practices-puerto-paritychecklist before execution to confirm agents, dependencies, deliverables.
Workflow
- Channel Mapping – assign assets to channels with timing, CTA, and owner.
- Publishing Prep – outline CMS/social scheduler steps, asset variants, localization, and approvals.
- Amplification Plan – coordinate paid boosts, influencer/partner drops, internal comms, enablement uploads.
- Measurement Hooks – define UTMs, dashboards, alerting, and reporting cadence.
- Feedback & Recycling – schedule retro checkpoints and repurposing opportunities.
Outputs
- Distribution calendar with timestamps, channels, owners, UTMs, and status.
- Amplification checklist (partners, paid, internal enablement, ABM tie-ins).
- Measurement + feedback plan.
- Plan JSON entry stored/updated in
.claude/plansfor audit trail.
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 · 20 tokens per session scan A 7bbd1af8b94c
distribute-assets is a command published in the GitHub repository gtmagents/gtm-agents (398 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 696 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.