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 boshi-xixixi/TraeSkill --skill gtm-product-led-growthgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/gtm-product-led-growth)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/gtm-product-led-growth"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/gtm-product-led-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/boshi-xixixi/traeskill/gtm-product-led-growth"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/gtm-product-led-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.00060 | $0.03004 |
| Opus 5 | $0.00030 | $0.01502 |
| Sonnet 5 | $0.00012 | $0.00601 |
| Haiku 4.5 | $0.00006 | $0.00300 |
Grade A, and why
gtm-product-led-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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- product-led-growth — 95% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product-Led Growth
Build self-serve acquisition and expansion motions. But first, figure out if PLG is even the right motion for your product.
When to Use
Triggers:
- "Should we build PLG or sales-led?"
- "How do we drive self-serve adoption?"
- "Freemium to paid conversion isn't working"
- "Developer-led adoption strategy"
- "Which growth channels should we invest in?"
- "How do I know if PLG will work?"
Context:
- Developer tools and platforms
- B2B SaaS with self-serve potential
- Products where value is obvious without demo
- Bottom-up adoption motions
- Growth channel prioritization
Core Frameworks
1. The PLG Reality Check (Test Before You Commit)
What I Learned Running Both Motions in Parallel:
Classic startup debate. PLG camp: "Developers want self-serve." Sales camp: "Enterprises need hand-holding." Instead of arguing, we tested both for 6 months. Same product, two GTM motions, tracked everything.
The Results:
PLG: High volume, low ACV ($5K), fast time-to-revenue, higher churn. Sales-led: Lower volume, high ACV ($50K), slower time-to-revenue, lower churn. Sales won 10x on dollars despite 10x less volume.
Why: Product complexity + buyer seniority = sales-led wins. The product required integration with existing infrastructure, change management across teams, and multi-stakeholder alignment. Developers loved self-serve. But they weren't the economic buyer.
PLG works when:
- Value is obvious in first 5 minutes
- Implementation is trivial
- Individual user gets value without team buy-in
- No procurement/legal hurdles
- Buyer = user
Sales-led works when:
- Product requires integration/setup
- Multiple stakeholders need alignment
- Buyer ≠ user
- Deal size justifies human touch
- Customer needs education to see value
Before building PLG, test your motion. Don't assume PLG is better because it's trendy. PLG is efficient at volume, but sales-led can be more profitable with complexity.
2. The Growth Equation (Map Inputs to Outputs)
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.
- 8d ago First seen · 340 lines · 60 tokens per session scan A c938e886e38c
gtm-product-led-growth is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 3,004 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.