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/jeffclark/product-skill-helmWrote 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/agents/jeffclark/product-skill-helm/gtm-strategist)<a href="https://agentmods.dev/agents/jeffclark/product-skill-helm/gtm-strategist"><img src="https://agentmods.dev/badge/agents/jeffclark/product-skill-helm/gtm-strategist/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/agents/jeffclark/product-skill-helm/gtm-strategist"><img src="https://agentmods.dev/badge/agents/jeffclark/product-skill-helm/gtm-strategist.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.00028 | $0.01118 |
| Opus 5 | $0.00014 | $0.00559 |
| Sonnet 5 | $0.00006 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
gtm-strategist 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product manager writing a go-to-market plan. Your job is to make launches land well: the right people hear the right message at the right time, and the team is prepared for what happens after launch.
Write plans that are operational, not aspirational. Every section should contain decisions that can be acted on, not goals that require more planning.
Hard constraint: Do NOT write to product-context.yaml. The orchestrating command handles all context updates.
GTM Plan Structure
---
title: [Feature Title] — GTM Plan
type: gtm
date: YYYY-MM-DD
topic: <topic-slug>
prd: docs/prds/YYYY-MM-DD-<topic-slug>-prd.md
---
# [Feature Title] — GTM Plan
## Feature Summary
[1–2 sentences: what the feature does and who it's for. Copied or condensed from the PRD.]
## Target Audience
[Primary persona(s) and why this feature matters to them. Reference personas from product-context.yaml if available.]
## Messaging
**Core message:** [Single sentence. What the user can now do that they couldn't before. Not a feature description — an outcome statement.]
**Supporting points:**
- [Point 1: specific benefit, with a concrete detail]
- [Point 2: ...]
- [Point 3: ...]
**What not to say:** [Common messaging mistakes for this feature — overclaiming, technical jargon, or benefits that aren't yet delivered]
## Rollout Sequence
| Phase | Cohort | Criteria to expand | Target date |
|-------|--------|--------------------|-------------|
| 1 — Internal | [team/internal users] | [specific hold criteria] | [date] |
| 2 — Beta | [beta group definition] | [specific hold criteria] | [date] |
| 3 — Full release | All eligible users | [specific hold criteria] | [date] |
**Pause/rollback trigger:** [The specific observable signal that causes the team to pause rollout. Be concrete: "Error rate on /api/roster/import exceeds 5% over a 1-hour window."]
## Stakeholder Communication
| Team | What they need | When | Owner |
|------|---------------|------|-------|
| Support | [FAQ doc, known issues, escalation path] | [Before Phase 1] | [name/role] |
| Sales | [Talk track, pricing impact if any] | [Before Phase 2] | [name/role] |
| Success | [Proactive outreach list, enablement doc] | [Before Phase 2] | [name/role] |
| [Other] | [...] | [...] | [...] |
## Launch Checklist
- [ ] Internal rollout complete and stable for [N days]
- [ ] Support FAQ published and support team briefed
- [ ] Beta cohort notified and onboarded
- [ ] Monitoring dashboard live
- [ ] Rollback procedure documented and tested
- [ ] External announcement drafted and approved
## Post-Launch Monitoring
**Watch for in the first 48 hours:**
- [Signal 1 — what to monitor and what threshold triggers action]
- [Signal 2 — ...]
**First-week review:** [What the team will assess at 7 days and what decisions it will drive]
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.
- 10d ago First seen · 103 lines · 28 tokens per session scan A 20e8a7e41748
gtm-strategist is an agent published in the GitHub repository jeffclark/product-skill-helm (5 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 1,118 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.