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 guia-matthieu/clawfu-skills --skill expansion-signalsgit clone --depth 1 https://github.com/guia-matthieu/clawfu-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/guia-matthieu/clawfu-skills/expansion-signals)<a href="https://agentmods.dev/skills/guia-matthieu/clawfu-skills/expansion-signals"><img src="https://agentmods.dev/badge/skills/guia-matthieu/clawfu-skills/expansion-signals/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/guia-matthieu/clawfu-skills/expansion-signals"><img src="https://agentmods.dev/badge/skills/guia-matthieu/clawfu-skills/expansion-signals.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.00024 | $0.03484 |
| Opus 5 | $0.00012 | $0.01742 |
| Sonnet 5 | $0.00005 | $0.00697 |
| Haiku 4.5 | $0.00002 | $0.00348 |
Grade A, and why
expansion-signals 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 9d 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expansion Signals
Detect opportunities for account expansion by analyzing usage patterns, growth indicators, and behavioral signals that predict readiness to buy more.
When to Use This Skill
- Monthly expansion pipeline review
- Identifying upsell candidates
- Prioritizing CSM expansion efforts
- Building expansion playbooks
- Forecasting expansion revenue
Methodology Foundation
Based on Lincoln Murphy's Expansion Revenue Framework and Gainsight Expansion Playbooks, focusing on:
- Usage ceiling signals
- Growth triggers
- Buying intent indicators
- Timing optimization
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Identifies expansion signals | Which opportunities to pursue |
| Scores expansion readiness | Pricing and packaging |
| Suggests conversation openers | Relationship approach |
| Prioritizes opportunities | Resource allocation |
| Calculates potential value | Discount/incentive offers |
What This Skill Does
- Signal detection - Identify expansion indicators
- Opportunity scoring - Rank expansion readiness
- Sizing estimation - Potential expansion value
- Timing recommendation - When to engage
- Conversation guidance - How to approach
How to Use
Analyze expansion signals for:
Account: [Company Name]
Current Contract: $[ARR]
Products: [What they have]
Contract End: [Date]
Usage Data:
- Seats: [Used] / [Licensed]
- Feature usage: [Which features, how much]
- Usage trend: [Growing/Flat/Declining]
- Power users: [How many, what they do]
Account Context:
- Company growth: [Hiring, funding, news]
- Stakeholder changes: [New decision makers]
- Requests: [Feature requests, complaints about limits]
Available Expansion:
- Additional seats: $[Price]
- New modules: [List with prices]
- Higher tier: $[Price difference]
Instructions
Step 1: Identify Expansion Signal Categories
Usage Ceiling Signals (Strong):
| Signal | What It Means |
|---|---|
| >90% seat utilization | Need more licenses |
| Hitting API limits | Need higher tier |
| Feature requests beyond plan | Ready for upgrade |
| Workarounds for limitations | Pain = opportunity |
| Power users maxing features | Champions for expansion |
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.
- 9d ago First seen · 497 lines · 24 tokens per session scan A d7cd0a4ac549
expansion-signals is a skill published in the GitHub repository guia-matthieu/clawfu-skills (149 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 3,484 once invoked, about $0.0001 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
ads-creative-development
How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns…
ads-performance-analytics
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media…
paid-media-strategy
A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media…
community-outreach
Systemneutrale Automatisierung für lösungsorientierten Community Outreach und Repo-Recommender in Foren, Reddit und Plattformen nach dem Human-in-the-Loop-Prinzip (EU AI Act konform).
error-log
Apply when learning from a mistake. Central memory of past errors and derived rules; consult before logging a new error to avoid duplicates.
python
Apply when writing Python code. Type hints, error handling, mutable defaults, async patterns, and packaging conventions.