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 expansion-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/expansion-signal)<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/expansion-signal"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/expansion-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/expansion-signal"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/expansion-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.00085 | $0.00617 |
| Opus 5 | $0.00043 | $0.00309 |
| Sonnet 5 | $0.00017 | $0.00123 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
expansion-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 11d 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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expansion Signal
The other act-skill on the right side. Two of the three ways a company grows happen after the first sale (docs/operating-model.md), and this is one of them: account-health flags the EXPANSION-SIGNAL; this turns it into an angle and hands it to sales with the customer context attached — so it isn't a cold internal restart.
From the healthy account in ops/customers.md and the EXPANSION-SIGNAL line:
- Confirm the trigger is real. Expansion rides on adoption, not the calendar. The signal is the core used well plus a named next pain — a second team asking unprompted, a new use case, more seats. A renewal date is not an expansion trigger; pushing growth on an account that isn't getting value yet is churn with extra steps.
- Name the angle. Which way does it grow — an adjacent team, a new use case, deeper use of what they already have? Is it cross-sell (a new thing) or more of the same (more seats, more volume)? One angle, named.
- Build the case on realized value. Start from what they've already gotten — the outcome the book can show — and extend it to the new area, in their words, not a feature list.
- Re-arm the champion. Expansion is carried internally, not pitched in. Give the champion the one-page case they can forward, and the line that makes it their idea — not your quota.
- Hand to sales with the CS context. The handoff is the account, the angle, the realized-value case, and the champion — so sales picks up a warm, qualified expansion, not a cold account. A real expansion is a new deal: it crosses back to
ops/pipeline.md, the loop the bowtie closes. - Log it and update the book. Mark the account Expanding; note the angle and the handoff in
ops/customers.md.
Don't run this on an unhealthy account — route that to churn-save first. Expansion is the reward for value landing, not a substitute for it.
Depth
- quick: confirm the trigger + name the one angle.
- standard: the full play — trigger, angle, value-case, champion, hand to sales.
- deep: + the multi-thread map of who signs off on the larger spend, and the buyer-facing one-pager for the champion to forward.
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.
- 11d ago First seen · 25 lines · 85 tokens per session scan A f91454bc2654
expansion-signal is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 4d ago), licensed MIT. It adds 85 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.