sales-objection-sorter

sales-objection-sorter is a skill for Claude Code, Codex from jpeslar1/john-peslar-ai-skills. It costs 47 tokens per session (788 once invoked), scanned A, original, MIT.

A process for sorting sales objections and choosing a respectful response. Sales objections are buyer concerns about issues such as price, timing, authority, risk, or getting more information.

In plain words
What is it for?
Use it to classify objections, ask neutral menu-style questions, and decide whether a sensible next step exists.
Why use it?
It helps distinguish a real fit problem from a concern that needs clarification without treating every objection as a reason to pressure the buyer. It keeps responses tied to the actual conversation.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the sales-101 plugin — 10 skills shipped together

Good fit Use it to classify objections, ask neutral menu-style questions, and decide whether a sensible next step exists.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter
Install

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.

Any agent
npx skills add jpeslar1/john-peslar-ai-skills --skill sales-objection-sorter
Clone the repo
git clone --depth 1 https://github.com/jpeslar1/john-peslar-ai-skills

Made for: Claude Code, Codex.

Or install sales-101, the plugin that ships this one along with the rest of its 10 skills.

Wrote 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.

agentmods badge for sales-objection-sorter

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter/github.svg)](https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter)
Your own site
<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter/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.

agentmods 80×15 button for sales-objection-sorter

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-objection-sorter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00788
Opus 5 $0.00023 $0.00394
Sonnet 5 $0.00009 $0.00158
Haiku 4.5 $0.00005 $0.00079

Measured 3d ago against content hash 56c4d0f190e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sales-objection-sorter 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 3d 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.

sales-objection-sorter/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sales Objection Sorter

Treat objections as information about fit. Help the user understand the buyer's concern and decide whether there is a sensible next step. Do not turn a clear no into a script for pressure.

Read the objection in context

Use the exact wording, preceding exchange, deal stage, offer/price, known constraints, and authority path. Separate what was said from possible interpretations. If the user asks about common objections without a real thread, label the examples hypothetical.

Choose the top three real objections if supplied. Do not invent a buyer's hidden fear and state it as fact. Classify possible causes such as affordability, unclear value, insufficient evidence, competing priorities, wrong scope, or missing approval.

Ask a menu question, then listen

A useful menu offers two or three plausible interpretations and an open escape, without forcing agreement:

  • Price: "Is the issue the available budget, uncertainty about the return, or something else?"
  • Timing: "Is this waiting on another priority, an approval, or something else?"
  • More information: "Would scope, pricing, or how the pilot works be most useful, or is there another question?"

Tailor the options to facts. Ask one question and wait for the answer in live coaching; do not overwhelm the buyer with a full decision tree. In a prepared playbook, show branches clearly as possible future responses.

Map the answer to action:

  • Real budget mismatch: narrow scope sustainably or decline.
  • Value unclear: clarify the buyer's outcome and evidence without inventing ROI.
  • Delivery risk: offer bounded proof or a pilot with measurable acceptance.
  • Another approver: understand criteria and propose a joint next step.
  • Later priority: use the buyer's actual date or trigger, if they want a revisit.
  • Wrong problem, clear refusal, or no acceptable decision path: thank them and close.

Do not use a discount as the automatic answer to every price objection. Do not promise refunds, scope, or timelines the seller has not authorized.

Read the full file on GitHub · 56 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 3d ago First seen · 56 lines · 47 tokens per session scan A 56c4d0f190e1

Subscribe to this mod's changes

sales-objection-sorter is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 788 once invoked, about $0.0002 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-09.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens