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 uthumany/uthy-legacy-os --skill go-to-marketgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/go-to-market)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/go-to-market"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/go-to-market/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/uthumany/uthy-legacy-os/go-to-market"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/go-to-market.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.00035 | $0.00772 |
| Opus 5 | $0.00017 | $0.00386 |
| Sonnet 5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
go-to-market 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go-to-Market Strategy
Overview
A Go-to-Market (GTM) strategy answers: Who are we selling to? What do we say? How do we reach them? Why will they buy? This skill covers GTM planning for features and products — from positioning and messaging to channel selection and launch timing.
When to Use
- Launching a new product or major feature
- Entering a new market segment
- Changing pricing or packaging
- You need a coordinated plan across product, marketing, sales, and success
- Don't use for: minor feature releases (use the launch-plan skill), internal tools
Instructions
1. Define Target Segments
Who is this for? Be specific:
- Primary segment: Who will buy first?
- Secondary segment: Who will buy next?
- Explicitly NOT for: Who should NOT buy this? (helps positioning)
2. Craft Positioning
Use the elevator-pitch skill. Then:
- Category: What category are you competing in?
- Differentiation: The 1-2 things you do uniquely well
- Proof points: Evidence that backs your claims (metrics, testimonials, case studies)
3. Choose Channels
How will you reach each segment?
| Channel | Best For | Effort Level |
|---|---|---|
| In-app announcements | Existing users | Low |
| Existing users, warm leads | Medium | |
| Blog/content | Top of funnel, SEO | High |
| Social media | Awareness | Low-Medium |
| Sales outreach | Enterprise | High |
| Partners/GTM alliances | New segments | High |
| Community | Developer/creator products | Medium |
4. Define Pricing & Packaging
- Is this included in existing plans, or a new SKU?
- What pricing tier does it unlock?
- Is there a trial or freemium path?
5. Set Launch Tiers
- Soft launch: Existing users only. Low-risk, get feedback
- Limited launch: Waitlist or invite-only. Build demand
- Broad launch: Open to all. Full marketing campaign
- Enterprise launch: Account-based. Sales-led with custom SLAs
6. Create the GTM Calendar
Coordinate across teams:
- Product: When will it be ready?
- Marketing: When are assets ready?
- Sales: When is enablement done?
- Support: When is training complete?
- Success: When does onboarding start?
- Key dates: Announce date, Launch date, Triage window
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 · 88 lines · 35 tokens per session scan A 7034ddb32c21
go-to-market is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 772 once invoked, about $0.0002 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-31.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…