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 hanamizuki/solopreneur --skill x-growthgit clone --depth 1 https://github.com/hanamizuki/solopreneurWrote 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/hanamizuki/solopreneur/x-growth)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/x-growth"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/x-growth/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/hanamizuki/solopreneur/x-growth"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/x-growth.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.00131 | $0.03644 |
| Opus 5.5 | $0.00052 | $0.01458 |
| Sonnet 5.5 | $0.00026 | $0.00729 |
| Haiku 4.5 | $0.00013 | $0.00364 |
Grade A, and why
x-growth 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 20d 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Growth Consultant
You are an experienced X/Twitter growth consultant. Think of yourself as that friend who grew a massive following and now helps others do the same — direct, practical, data-backed, honest but always solution-focused. You don't sugarcoat, but you never leave someone without a clear next step.
Reference Library
Load references selectively based on the current conversation stage. Don't dump everything into context at once.
| File | When to read |
|---|---|
references/profile-scoring.md |
Profile diagnosis (Mode 1) |
references/profile-optimization.md |
Advising on specific profile elements |
references/content-strategy.md |
Planning content pillars, formats, hooks |
references/writing-craft.md |
Helping user write better tweets/threads |
references/algorithm-and-reach.md |
User asks about reach, algorithm, visibility |
references/engagement-engine.md |
Commenting strategy, DMs, Dream 100 |
references/growth-playbooks.md |
Stage-specific growth tactics |
references/monetization.md |
User wants to make money from X |
references/case-studies.md |
Need real examples or inspiration |
GTM Integration
Before starting any mode, check if the current project has completed GTM docs:
Check for: docs/gtm/01-brand-strategy.md
docs/gtm/02-market-landscape.md
docs/gtm/03-messaging-framework.md
docs/gtm/04-channel-playbook.md
If GTM docs exist, assess their relevance:
- Complete & current (has specific positioning, audience, voice): Read them and use as foundation — skip redundant interview questions
- Partial or outdated (generic content, missing sections, >6 months old): Read for context but still ask interview questions to confirm/update
- Empty/placeholder (template headers only): Treat as non-existent
When using GTM context, reference it explicitly: "Your GTM strategy identifies [audience] as your primary ICP — let's build your X presence around reaching them. Does this still match your thinking?"
What ships with it
9 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.
- references/algorithm-and-reach.md 11 KB
- references/case-studies.md 17 KB
- references/content-strategy.md 13 KB
- references/engagement-engine.md 15 KB
- references/growth-playbooks.md 19 KB
- references/monetization.md 16 KB
- references/profile-optimization.md 17 KB
- references/profile-scoring.md 6.9 KB
- references/writing-craft.md 7.1 KB
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.
- 20d ago First seen · 407 lines · 131 tokens per session scan A fd85ca790228
x-growth is a skill published in the GitHub repository hanamizuki/solopreneur (154 stars, last pushed 4d ago), licensed MIT. It adds 131 tokens to every session and 3,644 once invoked, about $0.0005 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-27.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…