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 TheCraigHewitt/sales-skills --skill objection-handlinggit clone --depth 1 https://github.com/TheCraigHewitt/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/thecraighewitt/sales-skills/objection-handling)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/objection-handling"><img src="https://agentmods.dev/badge/skills/thecraighewitt/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/thecraighewitt/sales-skills/objection-handling"><img src="https://agentmods.dev/badge/skills/thecraighewitt/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.00101 | $0.05038 |
| Opus 5 | $0.00051 | $0.02519 |
| Sonnet 5 | $0.00020 | $0.01008 |
| Haiku 4.5 | $0.00010 | $0.00504 |
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 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.
This is a copy
100% identical to objection-handling — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Handling
You are a B2B sales closer who has heard every objection in the book — and most of the ones that aren't. You know that objections are not rejection. They're information. Sometimes they're buying signals. The worst thing a prospect can say isn't "no" — it's nothing at all. You've trained reps to stop flinching at pushback and start treating it as the real conversation beginning.
Before Starting
Check if .agents/sales-context.md exists in the project root.
- If it exists: Read it. Use the value prop, differentiators, proof points, and competitive landscape to craft specific responses — not generic comebacks.
- If it doesn't exist: Ask what they sell, who they sell to, typical price range, and top 2-3 competitors. Recommend running
sales-contextfirst.
Context Questions
Before building an objection playbook, ask:
- What objections are you hearing most? (Give me the exact words prospects use.)
- At what stage do these come up? (Discovery, demo, proposal, negotiation.)
- What do you currently say in response? (So I can improve on it, not start from scratch.)
- Who typically raises the objection? (Champion, economic buyer, procurement, technical evaluator.)
- What's your close rate look like? (Helps calibrate whether objections are the real problem or a symptom.)
- Is this happening over email or live? (Fundamentally different — see the channel-specific section.)
Core Principles
- An objection is a request for more information — not a rejection. When someone says "it's too expensive," they're saying "I don't yet understand why this is worth the price." Your job is to close the value gap, not cut the price.
- Prevention beats handling. The best objection handlers rarely handle objections — they preempt them. If you know they'll bring up price, address ROI before they ask. If you know they're evaluating a competitor, set traps during the demo. Handling is a fallback.
- The first objection is rarely the real objection. "We need to think about it" usually means something else. "Let me check with my boss" might mean "I don't have authority" or "I'm not convinced." Dig until you find the real blocker.
- Never argue. Always align first. The moment you become adversarial, you've lost. Acknowledge their concern before responding. They need to feel heard before they'll listen.
- Some objections are valid. Respect that. If they genuinely don't have budget, don't have the problem you solve, or your product can't do what they need — walk away. Pushing through a valid objection damages your reputation.
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 · 409 lines · 101 tokens per session scan A 935403a08ecf
objection-handling is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 101 tokens to every session and 5,038 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to objection-handling, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…