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 Doris-Labs/sales-skills --skill expansion-upsellgit clone --depth 1 https://github.com/Doris-Labs/sales-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/doris-labs/sales-skills/expansion-upsell)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/expansion-upsell"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/expansion-upsell/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/doris-labs/sales-skills/expansion-upsell"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/expansion-upsell.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.00074 | $0.01878 |
| Opus 5 | $0.00037 | $0.00939 |
| Sonnet 5 | $0.00015 | $0.00376 |
| Haiku 4.5 | $0.00007 | $0.00188 |
Grade A, and why
expansion-upsell 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expansion & Upsell
Purpose
Turn a happy (or quiet) existing account into the next deal: find what you haven't sold yet, judge whether they're ready to buy more, attach the ask to a moment of realized value, and produce a concrete expansion plan you can run.
Inputs
- The account: current products/seats/teams sold, contract value, renewal date
- Usage and adoption signals (who's active, what's stuck, where they hit a limit)
- Sentiment and relationship health (champions, detractors, exec exposure)
- What else you could sell (other products, more seats, adjacent teams, tiers)
Method
-
Whitespace map. Lay the account out as a grid: products you sell (rows) × teams/business units in the account (columns). Mark each cell sold / not-sold / in-trial. The blank cells are your whitespace. Add three more dimensions:
- Seats: licensed vs active vs total addressable headcount in sold teams.
- Tier/edition: are they on a plan below what their usage justifies?
- Adjacent teams: units using none of your product but with the same pain. Rank whitespace by (fit × reachability) — closest to an existing champion and most similar to a use case already winning wins first.
-
Read expansion-readiness signals. Do not pitch more to an account that hasn't realized value on what it already bought. Score readiness on:
- Adoption depth: active-seat ratio, frequency, breadth of features used. Healthy = a beachhead worth widening. Low = fix adoption before upselling.
- Value realized: has the customer hit the outcome you sold? Quantify it (time saved, deals influenced, cost avoided) — that number funds the next buy.
- Sentiment trend: is it improving or souring? Expand on a rising curve.
- Champion strength: is there someone who will advocate internally for spend? Green on adoption + value + sentiment = expand now. Any red = remediate first.
-
Watch for expansion triggers. The ask lands when something changed:
- New executive / new budget owner — re-sell the value, ride a fresh agenda.
- New initiative / project / funding round — attach your product to their plan.
- Hitting a limit — seats maxed, usage capped, a tier ceiling reached. The limit is the pitch: they're already feeling the constraint.
- A new use case surfacing in conversation — a team or pain you don't yet serve.
- Renewal approaching — natural commercial moment to repackage and grow. Map each live trigger to the whitespace cell it unlocks.
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 · 138 lines · 74 tokens per session scan A 49cc2d30c1a0
expansion-upsell is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 1,878 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-31.
Other skills, from other repositories
lynqu
Entry point for the Lynqu sales suite — describe any sales situation and it composes the right skills across capture, outreach, quoting and reporting. Requires the Lynqu MCP server connected.
lynqu-sales-playbook
Turn a written sales playbook into a live Lynqu pipeline — contacts, timed tasks, follow-up templates, the playbook attached to each lead, and stage rules that deliver the prep at the right moment.
lynqu-card-studio
Create and update Lynqu digital business cards — contact info, social links, services, template, palette — and check card views, scans and shares. Requires the Lynqu MCP server connected.
lynqu-competitors
Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
lynqu-contacts
Map the buying committee on an account — economic buyer, champion, blocker — and write it into Lynqu as contacts and participants. Requires the Lynqu MCP server.
lynqu-deal-desk
Price a Lynqu deal and draft the quote — browse the price book, put priced lines on a deal, then produce a draft quote for a human to send. Requires the Lynqu MCP server connected.