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 saski/arnesto --skill product-led-growthgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/product-led-growth)<a href="https://agentmods.dev/skills/saski/arnesto/product-led-growth"><img src="https://agentmods.dev/badge/skills/saski/arnesto/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/saski/arnesto/product-led-growth"><img src="https://agentmods.dev/badge/skills/saski/arnesto/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.00083 | $0.00617 |
| Opus 5 | $0.00042 | $0.00309 |
| Sonnet 5 | $0.00017 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
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 7d 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 product-led-growth — 0 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Product-Led Growth (PLG)
What It Is
Product-Led Growth is a go-to-market strategy where the product itself drives acquisition, activation, retention, and monetization. Instead of relying on sales to close deals before users can try the product, PLG lets users experience value first and buy later.
The core insight: In PLG, the product does the selling. Users sign up, experience value through self-serve, and either convert themselves or become qualified leads for sales.
PLG is fundamentally Data-Led Growth (DLG). When you give away a free product, you get two things in exchange: broader reach (lower barrier to entry) and usage data that tells you which features correlate with conversion and retention. Without this data foundation, you're giving away your product for nothing.
When to Use It
Use PLG frameworks when you need to:
- Design a freemium or free trial model for a B2B SaaS product
- Add self-serve to a sales-led product to expand reach
- Optimize conversion from free to paid users
- Define product-qualified leads (PQLs) for your sales team
- Reduce customer acquisition cost through self-serve
- Build a hybrid PLG + sales motion (product-led sales)
- Diagnose why free users aren't converting to paid
When Not to Use It
- Highly complex products requiring customization
- Very small addressable market
- No individual use case exists
- You lack data infrastructure
- You want instant revenue impact — PLG takes 12+ months
Resources
People to follow:
- Elena Verna (Substack, LinkedIn) — PLG, PLS, growth strategy
- Hila Qu — PLG implementation, activation, growth teams
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.
- 7d ago First seen · 62 lines · 83 tokens per session scan A d44197d05a0e
product-led-growth is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 4d ago), licensed Unlicense. It adds 83 tokens to every session and 617 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to product-led-growth, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.