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 etrebels/claude-code-growth-os --skill product-signalgit clone --depth 1 https://github.com/etrebels/claude-code-growth-osWrote 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/etrebels/claude-code-growth-os/product-signal)<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/product-signal"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/product-signal/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/etrebels/claude-code-growth-os/product-signal"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/product-signal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.00606 |
| Opus 5 | $0.00032 | $0.00303 |
| Sonnet 5 | $0.00013 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
product-signal 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 10d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Signal
The product function's place in the loop. Marketing has marketing-feedback; CS has account-health; this is product's. It pulls the signals that should shape what gets built out of the shared log into product's own triage queue, and — for anything shipped — writes the one-line "what this means for the buyer" so a feature doesn't land silently. This closes handoffs H4 (CS→product) and H5 (product→GTM) in docs/operating-model.md.
From the shared feedback log (demo/feedback-log.md, or your own) and ops/customers.md:
- Pull the product-shaped signals. Three kinds belong on the roadmap, not in a meeting note:
RETENTION-RISKlines that are really a product gap — adoption friction or a missing capability, not a CS task.FEATURE-REQUESTitems that block an adoption or an expansion (the ones tied to a renewal or a second team).- Win/loss reasons that are about the product, not the deal — what we couldn't do that cost us, or won us, the deal.
- Route each into
ops/roadmap-signals.md. One row per signal: the source, the type, the account or pattern it's tied to, where it's routed, and a status (New → Routed → Shipped). This is product's working surface — distinct from the raw log it's pulled from. - Wait for the pattern on anything ambiguous. A single request isn't a roadmap item; a request that recurs across accounts, or one blocking a real renewal, is. Don't route noise.
- Close the loop on anything shipped. For each item that ships, write the one-line buyer-facing translation in the last column: what can the customer now do that they couldn't before — in their language, not the release note's. Hand that line to GTM (it's what
marketing-feedback's readers and the deal follow-ups need). No feature ships without it — the antidote to building things no one adopts.
Don't promise a roadmap; this routes the signal and frames the outcome. The build decision is yours.
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.
- 10d ago First seen · 26 lines · 65 tokens per session scan A bf4541abd048
product-signal is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 4d ago), licensed MIT. It adds 65 tokens to every session and 606 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-08-30.
Other skills, from other repositories
co-founder-dynamics
Complete co-founder playbook for technical founders — finding co-founders, equity splits (dynamic and static), co-founder agreements, vesting schedules, working relationships, conflict resolution, co-founder breakups, and the "dating before marrying" framework. Use when looking for a co-founder, structuring a founding…
support-tool-stack
Customer support platform selection, setup, and optimization — Intercom, Zendesk, Front, Help Scout, HubSpot Service Hub, Linear, and AI-native tools. Use when choosing a support platform, migrating tools, setting up help desk workflows, designing ticket routing, building macros and saved replies, or integrating…
advisor-recruitment
Strategic advisor recruitment for B2B SaaS founders. Use when building advisory board, recruiting individual advisors, structuring advisor compensation (equity grants), defining advisory scope, leveraging advisors for intros/references/customers, and managing ongoing advisor relationships.
engineer-to-founder
Translate engineering strengths into founder-led GTM: customer discovery, positioning, demos, technical proof, founder sales habits, and first repeatable motion. Use when a technical founder needs to sell, do customer interviews, explain value without feature dumping, or build GTM confidence.
first-hires-playbook
Complete playbook for founder's first 10 hires beyond sales. Use when hiring first engineer, first CS, first marketer, first product manager, or building founding team. Covers when to hire each role, job description architecture, compensation benchmarking, interview process design, and offer construction.
sla-management
Design and manage customer support SLAs — service level agreements, ticket priority matrices, first response time targets, resolution time targets, escalation paths, business hours configuration, and SLA performance dashboards. Use when defining support SLAs, building tier-based service levels, designing escalation…