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 The-Utopia-Studio/skills --skill growth-strategygit clone --depth 1 https://github.com/The-Utopia-Studio/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/the-utopia-studio/skills/growth-strategy)<a href="https://agentmods.dev/skills/the-utopia-studio/skills/growth-strategy"><img src="https://agentmods.dev/badge/skills/the-utopia-studio/skills/growth-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/the-utopia-studio/skills/growth-strategy"><img src="https://agentmods.dev/badge/skills/the-utopia-studio/skills/growth-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.00148 | $0.02302 |
| Opus 5.5 | $0.00059 | $0.00921 |
| Sonnet 5.5 | $0.00030 | $0.00460 |
| Haiku 4.5 | $0.00015 | $0.00230 |
Grade A, and why
growth-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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Strategy
Standardizes how growth strategy documents get built for Utopia Studio fellows, so every one — regardless of who authors it or which fellow it's for — has the same rigor, the same structure, and the studio's real brand instead of a generic template.
This skill was distilled from the first real growth strategy built this way (Pocket Health, August 2026), after an initial pass used a generic corporate template that turned out not to be close to the studio's actual brand. Treat that lesson as load-bearing: don't guess at branding when the real design system is one npm install away (see Brand System below).
When to use
Trigger whenever asked for a "growth strategy," "GTM strategy," "GTM plan," or "growth plan" for a named fellow. This produces an internal strategy memo (.docx), not a partner-facing pitch deck (utopia-partnership-deck is a different skill for that) and not board/investor material.
Before building: research first
Never start writing from the structure below until both halves of the research are done. A document full of guessed facts or generic placeholders is worse than asking a clarifying question first.
Internal. Check wherever this fellow's materials live (an attached Claude project, uploaded docs, prior conversation) for existing strategy work: executive summaries, MVP/pilot plans, prior decks. Read them. The growth strategy should be consistent with decisions already made, not reinvent them. If nothing exists yet, say so plainly rather than fabricating a backstory.
External. Research the fellow's actual market:
- Who the real target customers are in each named market, with a specific, checkable reason each belongs on the list. Never write a placeholder like "a large enterprise" or "a major insurer" — name the company and say why.
- The regulatory/structural specifics of any market that isn't the fellow's home market, especially Qatar/the Gulf (the studio's home base — see
utopia-partnership-deck's "Why Doha" convention for why this lens usually belongs in Utopia work). Don't assume a new market mirrors the primary one; for example, a market may lack the public price/quality data infrastructure the primary market has, which changes what's achievable there in year one. - Named competitors and comparable companies, with what they actually do and where they fall short, if that context sharpens the value proposition.
What ships with it
3 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.
- 1mo ago First seen · 94 lines · 148 tokens per session scan A d9ed42180f91
growth-strategy is a skill published in the GitHub repository The-Utopia-Studio/skills (7 stars, last pushed today), licensed Apache-2.0. It adds 148 tokens to every session and 2,302 once invoked, about $0.0006 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-09-05.
Other skills, from other repositories
github
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending,"…
xml-sitemap
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate…
google-ads
When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube…
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic…
robots-txt
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine…
canonical-tag
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals. Also use when the user mentions "canonical," "canonical URL," "duplicate content," "duplicate content fix," "preferred URL," or "URL consolidation." For GSC duplicates, use google-search-console.