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 daffy0208/ai-dev-standards --skill go-to-market-plannergit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWrote 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/daffy0208/ai-dev-standards/go-to-market-planner)<a href="https://agentmods.dev/skills/daffy0208/ai-dev-standards/go-to-market-planner"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/go-to-market-planner/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/daffy0208/ai-dev-standards/go-to-market-planner"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/go-to-market-planner.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.00040 | $0.01767 |
| Opus 5 | $0.00020 | $0.00883 |
| Sonnet 5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
Go-to-Market Planner 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 12d 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.
This is a copy
100% identical to Go-to-Market-Planner — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go-to-Market Planner
Plan and execute successful product launches.
Core Principle
Launch is a campaign, not an event. Build momentum before launch, peak at launch, sustain after launch.
5-Phase GTM Strategy
Phase 1: Market Positioning
Goal: Define how product fits in market landscape
Positioning Statement:
For [target customer]
Who [customer need/problem]
[Product name] is a [product category]
That [key benefit/differentiation]
Unlike [competitors]
Our product [unique value]
Competitive Analysis:
| Competitor | Strengths | Weaknesses | Our Advantage |
|---|---|---|---|
| Competitor A | Feature X | Price | Better UX |
Validation:
- Target customer clearly defined
- Differentiation identified
- Positioning tested with 5+ customers
Phase 2: Messaging & Content
Goal: Create compelling launch messaging
Message Hierarchy:
- Headline: Core benefit in 5-10 words
- Sub-headline: How it works or who it's for (1 sentence)
- 3 Key Benefits: What users gain (feature → benefit)
- Social Proof: Testimonials, case studies, logos
- Call-to-Action: Clear next step
Content Types:
- Launch blog post
- Product demo video (2-3 min)
- Landing page
- Email announcement
- Social media posts (5-10 ready)
- Press release (if targeting media)
Validation:
- Messaging tested with target customers
- Content created 2 weeks before launch
- CTAs clear and trackable
Phase 3: Channel Strategy
Goal: Identify where to reach target customers
Channel Options:
Owned Channels (free, full control):
- Email list (existing customers/subscribers)
- Blog and SEO
- Social media (Twitter, LinkedIn)
- YouTube
Earned Channels (free, limited control):
- Press and media (TechCrunch, Product Hunt)
- Influencers and partners
- Community forums (Reddit, Hacker News)
- Word of mouth
Paid Channels (cost, full control):
What ships with it
2 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.
- 12d ago First seen · 306 lines · 40 tokens per session scan A caff213c18b7
Go-to-Market Planner is a skill published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It adds 40 tokens to every session and 1,767 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Go-to-Market-Planner, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…