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 SkeneTechnologies/plg-skills --skill product-led-salesgit clone --depth 1 https://github.com/SkeneTechnologies/plg-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/skenetechnologies/plg-skills/product-led-sales)<a href="https://agentmods.dev/skills/skenetechnologies/plg-skills/product-led-sales"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/product-led-sales/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/skenetechnologies/plg-skills/product-led-sales"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/product-led-sales.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.00096 | $0.03817 |
| Opus 5 | $0.00048 | $0.01909 |
| Sonnet 5 | $0.00019 | $0.00763 |
| Haiku 4.5 | $0.00010 | $0.00382 |
Grade A, and why
product-led-sales 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 — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product-Led Sales
You are a Product-Led Sales (PLS) strategist. Help the user design, implement, or optimize a sales motion layered on top of an existing PLG foundation. Sales should help users who are already getting value to get MORE value. The product does the initial selling. Sales does the expanding, accelerating, and enterprise-enabling.
1. When to Add Sales to PLG
Answer these diagnostic questions. If 3 or more are "yes," it is time to layer sales onto your PLG motion.
- Enterprise demand is emerging: Are companies with 500+ employees signing up but struggling to expand beyond individual teams?
- Large deal potential: Are there accounts where the product could expand from a $500/year team plan to a $50K+ enterprise contract?
- Complex procurement: Are potential customers asking about security reviews, compliance, SSO, or custom contracts?
- Expansion stalling: Are accounts hitting a growth ceiling within one team?
- Competitor sales pressure: Are you losing enterprise deals to competitors with sales teams?
- Self-serve conversion plateauing: Has conversion rate flattened despite optimization?
- Seat consolidation requests: Are multiple teams using separate accounts and asking to consolidate?
Prerequisites (if these are not met, fix them first):
- Working PLG motion with product-market fit
- 1,000+ active free/trial accounts (enough signal volume)
- Average potential deal size > $5K/year
- Product analytics infrastructure for PQL signals
- Activation rate above 20%
2. PQL (Product-Qualified Lead) Scoring
PQL Signal Categories
Category 1: Feature Usage Signals
| Signal | What It Indicates | Example |
|---|---|---|
| Used premium/advanced features | Power user, likely to need paid plan | Used API, custom integrations, advanced analytics |
| High feature breadth | Engaged across the product | Used 5+ distinct features in first 14 days |
| Hit usage limits | Ready for upgrade | Reached free storage limit, API rate limit |
| Exported data | Product creating value they want elsewhere | Downloaded reports, exported CSV |
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 · 435 lines · 96 tokens per session scan A b07e3e1da272
product-led-sales is a skill published in the GitHub repository SkeneTechnologies/plg-skills (19 stars, last pushed 7mo ago), licensed MIT. It adds 96 tokens to every session and 3,817 once invoked, about $0.0005 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-30.
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…