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/manage-production)<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/manage-production"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/manage-production/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/manage-production"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/manage-production.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.00675 |
| Opus 5 | $0.00010 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
manage-production 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: manage-production
Inputs
- pillar – reference pillar or campaign.
- assets – comma-separated asset types or names.
- tools – optional tools/platforms (Docs, Figma, Notion, CMS).
- qa – include QA/evidence plan (default true).
- localization – regions/languages requiring localization.
GTM Agents Pattern & Plan Checklist
Pulled from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- Pattern selection: Production typically runs pipeline (tasks → owners → feedback → QA → packaging). Use diamond when localization or QA evidence can run parallel; document choice in the plan header.
- Plan schema: Save or update
.claude/plans/plan-<timestamp>.jsonwith task IDs, asset references, tooling context, parallel groups, handoff requirements, error handling, and success criteria (on-time %, defect ceiling). - Tool hooks: Reference
docs/gtm-essentials.mdstack (Serena for CMS automation patches, Context7 for brand/legal standards, Sequential Thinking for retros, Playwright for accessibility/QA screens). - Guardrails: Default retry limit = 2 for failed QA; escalation ladder = Creative Producer → Editorial Director → Marketing Director.
- Review: Run
docs/usage-guide.md#orchestration-best-practices-puerto-paritybefore execution to confirm agents, dependencies, deliverables.
Workflow
- Task Breakdown – create tasks per asset (draft, design, review, localization, QA).
- Owner Assignment – map writers, designers, reviewers, approvers, and due dates.
- Feedback Loops – schedule review checkpoints, consolidate feedback instructions.
- QA Checklist – ensure brand, accessibility, legal, and technical requirements are validated.
- Asset Packaging – outline final delivery steps (naming conventions, metadata, storage paths).
Outputs
- Production tracker (task, owner, status, due date, dependencies, comments).
- QA/evidence log template.
- Asset handoff checklist with storage locations.
- 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 7532516682ce
manage-production is a command published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 675 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.