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 stefanoskarakasis/Product-Marketing-Skills --skill go-to-market-strategygit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/stefanoskarakasis/product-marketing-skills/go-to-market-strategy)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/go-to-market-strategy"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/go-to-market-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/stefanoskarakasis/product-marketing-skills/go-to-market-strategy"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/go-to-market-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.00060 | $0.04140 |
| Opus 5.5 | $0.00024 | $0.01656 |
| Sonnet 5.5 | $0.00012 | $0.00828 |
| Haiku 4.5 | $0.00006 | $0.00414 |
Grade A, and why
go-to-market-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 13d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go-to-Market-Strategy
How This Works
Assigns a launch tier and generates a complete GTM strategy brief grounded in your brain. Not a template-filler. A strategic thinking partner that interrogates scope before recommending resource investment.
The skill runs in 6 steps:
Step 0 — Load brain context (ICP, alternatives & positioning, proof points) and, if the user maintains /context/meta-patterns.md, guardrails logged there.
Step 1 — Intake: Initiative name, success metric (90 days), timeline.
Step 2 — Load brain silently (Sections 2, 3, 6).
Step 3 — Apply four-signal tier assignment (market impact, revenue potential, competitive urgency, resource requirement).
Step 4 — Generate full GTM brief (7 sections: strategic context, channels, metrics, competitive, proof points, timeline, next steps).
Step 5 — Learning Close: log the session to /context/skill-sessions.md.
Trigger
- When: Assigning a launch tier and building a full GTM strategy brief for a product, feature, pricing change, or market expansion.
- Not for: Chaining this with other skills into one program → use
workflow-orchestrator. Choosing which acquisition motion(s) to invest in → usegtm-motionsbefore this skill if Channel Strategy needs real motion-fit backing. Messaging and positioning work itself → usepositioning-messagingafter this skill. Risk analysis → usepre-mortemafter this skill. Post-launch review → useretro. - Example prompts:
- "What tier is this launch?"
- "GTM strategy for our new pricing page"
- "Help me scope this feature launch"
- "How should we launch this?"
- "Plan my launch"
Inputs
- Args: Initiative name, 90-day success metric, timeline. Free format — Step 1 intake fills gaps conversationally.
- Defaults: If brain is missing or Section 2 (ICP) is empty, this skill sends the user to
beachhead-segment(same plugin) first — see Pre-flight and Step 0. - Context keys:
/foundation/brain.md— required. Sections 2 (ICP), 3 (Alternatives & Positioning), 6 (Proof Points Registry). Section 7 (Strategy) is read if present./context/meta-patterns.md— optional; recurring patterns the user has logged from prior GTM briefs.- Brain contract: Reads Sections 1 (
business_modelonly), 2, 3, 6, and 7 if present (launch calendar and priorities, to flag clashes with the new launch;conversion_actionas the default success action). Writes: none — this skill does not write to/foundation/brain.mdon its own. If Section 6 is thin or unsourced, route toproof-points(Add or Audit mode) rather than treating flagged claims as usable.
What ships with it
4 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.
- 13d ago Changed · +3 lines · -11 tokens per session adb5a188a507
- 18d ago Changed ffb5d4b589e3
- 21d ago Changed · +2 lines 83c944220e39
- 22d ago Changed 10646d22226f
- 27d ago Changed · +3 lines 398b22aa5de3
- 28d ago Changed · +13 lines 466f10aacce0
- 1mo ago Changed · +1 lines 3267fd2bdf28
- 1mo ago Changed ad02a873df9a
- 1mo ago Changed · +3 lines 4b7d8a206ff8
- 1mo ago First seen · 320 lines · 71 tokens per session scan A b24ce405ecbc
go-to-market-strategy is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 4,140 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
report
A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.
k8s-rightsize
Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".
owasp-security
Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.
fig
One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
workspace-rules
A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.