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 kazdenc/builder-skills --skill gtmgit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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/kazdenc/builder-skills/gtm)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/gtm"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/gtm/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/skills/kazdenc/builder-skills/gtm"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/gtm.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.00066 | $0.01729 |
| Opus 5 | $0.00033 | $0.00864 |
| Sonnet 5 | $0.00013 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
gtm 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 9d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a go-to-market plan that gets a product or feature from "built" to "adopted." Work through each step in order. Skip nothing.
Step 1: Understand What's Launching
Gather these before doing anything else:
| Question | Why it matters |
|---|---|
| What exactly is shipping? | Scope the plan — a whole product vs. a settings toggle need different launches |
| Who is the target audience? | Channels, messaging, and tier all depend on this |
| What's the timeline? | Determines what's realistic |
| What exists already? | Don't rebuild — reuse positioning, assets, channels that work |
| What's the business goal? | Growth, retention, expansion, awareness — each changes the plan |
If the user hasn't provided this context, ask. Don't guess.
Step 2: Positioning
Answer three questions clearly:
- Who is this for? Be specific. "Small business owners who manage their own payroll" not "SMBs."
- What job does it serve? Use the JTBD frame — what progress is the user trying to make? (Reference the jtbd skill if available.)
- How is it different? State the alternative the user has today and why this is better. If you can't articulate the difference, the positioning isn't ready.
Write it as a positioning statement:
For [target audience] who [situation/need],
[product/feature] is a [category]
that [key benefit].
Unlike [alternative], it [differentiator].
Step 3: Messaging
Build a messaging hierarchy:
| Layer | What it is | Example |
|---|---|---|
| Headline | The one sentence a stranger reads | "Ship invoices in 30 seconds, not 30 minutes" |
| Value proposition | The promise — what changes for the user | "Automated invoicing that pulls line items from your project tracker" |
| Proof points (3 max) | Evidence the promise is real | "Cuts invoice creation time by 90%" / "Syncs with Jira, Linear, Asana" / "Used by 2,000 teams in beta" |
Messaging template:
HEADLINE:
[One clear sentence. Lead with the outcome, not the feature.]
VALUE PROP:
[What the user gets. Focus on the job, not the technology.]
PROOF POINTS:
1. [Quantified result or social proof]
2. [Capability that matters most]
3. [Trust signal — security, reliability, adoption]
OBJECTION HANDLING:
- "Why should I switch?" → [Answer]
- "Is it reliable?" → [Answer]
- "What does it cost me to try?" → [Answer]
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.
- 9d ago First seen · 166 lines · 66 tokens per session scan A 145912901cc8
gtm is a skill published in the GitHub repository kazdenc/builder-skills (45 stars, last pushed 6mo ago), licensed MIT. It adds 66 tokens to every session and 1,729 once invoked, about $0.0003 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-30.
Other skills, from other repositories
commercial-opportunity-review
Review Product, offering, catalog, quote, and sale evidence for commercial opportunities.
demand-triage
Prepare classification, evidence gaps, and score inputs for product demand without crossing the funding boundary.
investment-preparation
Prepare an evidence-linked product investment packet while preserving the governed funding decision.
outcome-review
Review whether a funded product bet changed its intended outcome and append evidence-backed learning.
product-line-performance-review
Roll real Product evidence into a ProductLine review without changing the canonical reporting boundary.
stakeholder-brief
Prepare a concise owner or stakeholder brief with current decisions, evidence, bets, outcomes, roadmap, and provenance.