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.
npx skills add nicepkg/ai-workflow --skill prd-v09-gtm-strategygit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/skills/nicepkg/ai-workflow/prd-v09-gtm-strategy)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/prd-v09-gtm-strategy"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/prd-v09-gtm-strategy.svg" alt="Measured on agentmods" 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.00094 | $0.02412 |
| Opus 5 | $0.00047 | $0.01206 |
| Sonnet 5 | $0.00019 | $0.00482 |
| Haiku 4.5 | $0.00009 | $0.00241 |
Grade A, and why
prd-v09-gtm-strategy 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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Strategy
Position in workflow: v0.8 Monitoring Setup → v0.9 GTM Strategy → v0.9 Launch Metrics
Purpose
Define how the product reaches its target users—the channels, messaging, timing, and coordination required for a successful launch.
Core Concept: Launch as Campaign
A launch is not "making the product available." It is a coordinated campaign that creates awareness, drives activation, and captures feedback. Every touchpoint should move users toward value.
GTM Components
| Component | Purpose | Output |
|---|---|---|
| Messaging | What we say | GTM- (value props, headlines) |
| Channels | Where we say it | GTM- (channel strategy) |
| Timing | When we launch | GTM- (timeline, phases) |
| Coordination | Who does what | GTM- (RACI, tasks) |
Execution
-
Review target personas
- Pull PER- from v0.4
- Understand where they spend time
- Know what messages resonate
-
Define core messaging
- Value proposition (from CFD- value hypotheses)
- Positioning (from BR- product type)
- Key differentiators (from v0.2 competitive landscape)
-
Select launch channels
- Match channels to personas
- Prioritize by reach and conversion potential
- Consider owned, earned, and paid media
-
Plan launch timeline
- Pre-launch: Build anticipation
- Launch day: Maximum impact
- Post-launch: Sustain momentum
-
Assign ownership
- Who creates content?
- Who monitors channels?
- Who handles support surge?
-
Create GTM- entries with full traceability
GTM- Output Template
GTM-XXX: [GTM Item Title]
Type: [Messaging | Channel | Timeline | Task | Asset]
Owner: [Person or team responsible]
Status: [Planned | In Progress | Ready | Live]
For Messaging Type:
Audience: [PER-XXX targeted]
Format: [Headline | Value Prop | Tagline | Elevator Pitch]
Message: [The actual copy]
Supporting Evidence: [CFD-XXX value hypothesis it's based on]
Where Used: [GTM-YYY channels, assets]
For Channel Type:
Channel: [Specific platform or medium]
Audience Fit: [Why this channel reaches PER-XXX]
Strategy: [How we'll use this channel]
Content Plan: [What content goes here]
Success Metric: [How we measure effectiveness]
Linked Assets: [GTM-YYY assets for this channel]
For Timeline Type:
Phase: [Pre-launch | Launch Day | Week 1 | Month 1]
Date: [Specific date or relative timing]
Activities: [What happens in this phase]
Dependencies: [What must be ready]
Milestones: [Key checkpoints]
For Task Type:
Task: [What needs to be done]
Owner: [Who is responsible]
Due: [When it's due]
Dependency: [What it depends on]
Deliverable: [What's produced]
For Asset Type:
Asset: [What this is — landing page, email, video]
Purpose: [What it accomplishes]
Channel: [GTM-YYY where it's used]
Copy: [GTM-YYY messaging used]
Status: [Draft | Review | Approved | Live]
Linked IDs: [PER-XXX, CFD-XXX, KPI-XXX related]
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 287 lines · 94 tokens per session scan A 9664207d4282
prd-v09-gtm-strategy is a skill published in the GitHub repository nicepkg/ai-workflow (282 stars, last pushed 7mo ago), licensed MIT. It adds 94 tokens to every session and 2,412 once invoked, about $0.0005 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 skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.