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 discovery-callgit 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/discovery-call)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/discovery-call"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/discovery-call/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/discovery-call"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/discovery-call.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.00063 | $0.01471 |
| Opus 5 | $0.00032 | $0.00736 |
| Sonnet 5 | $0.00013 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
discovery-call 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Call
Purpose
Run a discovery call that gets the buyer talking, surfaces and quantifies the pain behind their interest, qualifies the deal, and ends with a confirmed next step — not a vague "let's circle back."
Inputs
- Who you're meeting and their role (economic buyer, champion, user, blocker?)
- What you already know about the deal/account (prior calls, inbound trigger, CRM)
- The single thing you need this call to advance (problem clarity? next meeting? access to power?)
Method
1. Run a SPIN-style question ladder. Move through four stages — never open with your product. Each stage earns the right to the next:
- Situation — establish the lay of the land. Keep these few and fast; buyers resent being interrogated about facts you could have researched. "Walk me through how your team handles X today." / "Who owns that process?"
- Problem — surface dissatisfaction. "Where does that break down?" / "What's the most frustrating part of that today?" / "How often does that bite you?"
- Implication — make the problem expensive. This is the stage reps skip and the one that creates urgency. "When that slips, what's the downstream cost?" / "Who else feels it when that happens?" / "What does that do to your number / your team's time?"
- Need-payoff — let the buyer articulate the value of solving it. "If you could make that go away, what would it be worth?" / "What would solving this free your team to do?" Buyers convince themselves when they say the payoff out loud.
2. Quantify the pain in the moment. A problem without a number is a hobby. Before you leave any pain, anchor it:
- Frequency × cost: "How many times a month? And roughly what does each one cost you in hours or dollars?"
- Baseline → target: "Where is it now? Where does it need to be?"
- Cost of inaction: "What happens if nothing changes by [date]?" Write the number down and feed it back: "So that's ~£X a quarter — did I get that right?" The confirmed number becomes your business case.
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 · 111 lines · 63 tokens per session scan A eb03e2902ae3
discovery-call is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,471 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-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.