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 aneja5/forge-skills --skill gtm-strategygit clone --depth 1 https://github.com/aneja5/forge-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/aneja5/forge-skills/gtm-strategy)<a href="https://agentmods.dev/skills/aneja5/forge-skills/gtm-strategy"><img src="https://agentmods.dev/badge/skills/aneja5/forge-skills/gtm-strategy/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/aneja5/forge-skills/gtm-strategy"><img src="https://agentmods.dev/badge/skills/aneja5/forge-skills/gtm-strategy.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.00061 | $0.01318 |
| Opus 5 | $0.00030 | $0.00659 |
| Sonnet 5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
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 6d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Strategy
Overview
Read .forge/prd.md and .forge/competitive.md to produce .forge/gtm.md — a concrete go-to-market plan. The output must be specific enough that a sales team can execute it without verbal briefing. ICP is a named persona, not a market segment.
When to Use
.forge/prd.mdexists and the product is approaching market readiness- User asks "how do we sell this" or "who do we sell to first"
- Competitive analysis is done and positioning is clear
- Need a pilot program design or ROI framework
When NOT to Use
- No PRD exists — run
spec-driven-developmentfirst - Product is pre-idea — run
idea-grillerfirst - User wants to refine the product, not sell it — use
spec-driven-development
Common Rationalizations
| Thought | Reality |
|---|---|
| "Our ICP is SMBs" | That's a market segment, not a person. Name the title, company size, and daily pain |
| "The product sells itself" | No product sells itself. Name the channel, motion, and first touchpoint |
| "We'll figure out pricing later" | Pricing shapes positioning. A free tool and a $500/mo platform attract different buyers |
| "ROI is hard to quantify" | If the buyer can't calculate ROI, they can't justify the purchase internally |
| "We don't need a pilot — just launch" | Pilots generate case studies. Case studies close deals. No pilot = no proof |
Red Flags
- ICP is a market segment ("SMBs", "enterprises") instead of a named persona
- Wedge feature is the entire product (not a wedge — it's the whole door)
- Sales channel is "inbound" with no specifics on content strategy or distribution
- ROI calculator uses aspirational numbers instead of conservative estimates
- Pilot has no success criteria or timeline
- Case study template doesn't include quantified before/after
Core Process
Step 1: Define ICP
Name the person, not the market:
- Title: specific role (e.g., "VP of Sales at a 50-200 person B2B SaaS company")
- Daily pain: what frustrates them this week, not abstractly
- Current solution: what they do today (the status quo from competitive analysis)
- Budget authority: can they sign a check, or do they need approval?
- Where they hang out: conferences, communities, publications, Slack groups
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.
- 6d ago First seen · 116 lines · 61 tokens per session scan A fdbf161d16cb
gtm-strategy is a skill published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 1,318 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-09-03.
Other skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
implement
Use when implementing a spec or GitHub ticket in this checkout.
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
run-smoke-tests
Run Playwright smoke tests, debug failures, and verify fixes. Use for smoke, e2e, Playwright, or pre-ship browser verification.
browser-use
Drive a real browser to QA a running app. Screenshots, clicks, forms, evidence. Use when there is no Playwright suite, or when a human flow must be walked.
tdd
Use when implementing features or bug fixes test-first.