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 objection-handlinggit 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/objection-handling)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/objection-handling"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/objection-handling/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/objection-handling"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/objection-handling.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.01736 |
| Opus 5 | $0.00032 | $0.00868 |
| Sonnet 5 | $0.00013 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
objection-handling 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Handling
Purpose
Turn a buyer's objection into a response that lowers the temperature, surfaces the real concern, and reframes the conversation around their stated problem — backed by what they actually told you on the calls.
Inputs
- The exact objection (their words, not your paraphrase)
- Who said it and their role (champion, economic buyer, blocker)
- The deal's stage, the value drivers that have landed, and competitors in play
Method
The core technique: Acknowledge → Clarify → Reframe → Evidence
Run every objection through these four beats in order. Skipping straight to a rebuttal is what makes reps sound defensive.
- Acknowledge — name the concern as legitimate before answering. Lowers defensiveness and buys you the right to ask a question. "That's fair — price has to map to the return, especially this quarter."
- Clarify — ask one question to find the concern under the objection. Most objections are proxies. "Too expensive" can mean no budget, no perceived value, or a competitor is cheaper — these need different responses. "When you say expensive, is it the number itself, or that the ROI isn't clear yet?"
- Reframe — move from their frame (cost / risk / effort) to the frame that helps you (outcome / cost of inaction / their own stated pain). "Let's put the price next to the £X the slipped deals are costing you each quarter."
- Evidence — close with proof, not assertion: a number they gave you, a quote from their own team, a comparable customer, the cost of the status quo.
Objection vs. brush-off
Decide which you're facing before you respond — they need opposite plays.
- An objection is specific and engaged: it names a concern, asks a question, invites an answer ("How does this handle X?", "We already use Y"). Run the four-beat method on it.
- A brush-off is vague and disengaging: it's designed to end the conversation ("Send me some info", "Now's not a great time", "Let me think about it"). Don't argue it — re-qualify. Ask a question that forces a real reason: "Happy to — so I send the right thing, what would have to be true for this to be worth your time?" If you can't get a concrete concern back, it's a priority/fit problem, not an objection problem. Don't burn cycles overcoming a brush-off.
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 · 134 lines · 63 tokens per session scan A 0780255e5207
objection-handling 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,736 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.