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 tough-tongue/demo-prep-skills --skill objection-handlergit clone --depth 1 https://github.com/tough-tongue/demo-prep-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/tough-tongue/demo-prep-skills/objection-handler)<a href="https://agentmods.dev/skills/tough-tongue/demo-prep-skills/objection-handler"><img src="https://agentmods.dev/badge/skills/tough-tongue/demo-prep-skills/objection-handler/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/tough-tongue/demo-prep-skills/objection-handler"><img src="https://agentmods.dev/badge/skills/tough-tongue/demo-prep-skills/objection-handler.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.00038 | $0.01481 |
| Opus 5 | $0.00019 | $0.00740 |
| Sonnet 5 | $0.00008 | $0.00296 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
objection-handler 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Handler
Generate thoughtful responses to sales objections. Provides multiple response options with different tones and explains the psychology behind each approach.
When to Use
- User says "How do I respond to: [objection]?"
- User is preparing for a meeting and wants to rehearse objection handling
- User encountered an objection on a call and wants better responses for next time
- User wants to build an objection library for their team
Required Inputs
Objection: [The exact words the prospect said, or a paraphrase]
Context: [Optional — who said it, what company, what stage of the conversation]
Process
1. Load Context
Read company-profile.md for:
- The user's standard objection responses (if they've filled them in)
- Product differentiators (ammunition for responses)
- Pricing information (for budget objections)
- Competitor positioning (for competitive objections)
2. Classify the Objection
Every objection falls into one of these categories:
| Category | What They're Really Saying | Example |
|---|---|---|
| Price / Budget | "I can't justify the cost" | "It's too expensive" / "We don't have budget" |
| Timing | "Not a priority right now" | "Check back next quarter" / "We're too busy" |
| Authority | "I can't make this decision alone" | "I need to run this by my manager" |
| Need | "I don't see why we need this" | "We're fine with our current process" |
| Trust | "I don't trust this will work" | "We tried something like this before" / "AI isn't good enough" |
| Competition | "We already have something" | "We use [competitor]" / "We're building this ourselves" |
| Stall | "I want to avoid saying no" | "Send me more info" / "Let me think about it" |
3. Generate Responses
For each objection, provide three response options with different approaches:
Output Format
## Objection: "[The exact objection]"
**Category:** [Price / Timing / Authority / Need / Trust / Competition / Stall]
**What they're really saying:** [The underlying concern beneath the surface objection]
---
### Response 1: Acknowledge and Redirect
> "[Response that validates their concern, then reframes the conversation]"
**Why this works:** [1 sentence explaining the psychology]
### Response 2: Quantify the Cost of Inaction
> "[Response that helps them see the cost of NOT solving the problem]"
**Why this works:** [1 sentence explaining the psychology]
### Response 3: Reduce the Risk
> "[Response that lowers the barrier — pilot, trial, smaller commitment]"
**Why this works:** [1 sentence explaining the psychology]
---
**Follow-up question to regain control:**
> "[A question that moves the conversation forward regardless of which response you use]"
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 · 142 lines · 38 tokens per session scan A 72ff275ba334
objection-handler is a skill published in the GitHub repository tough-tongue/demo-prep-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,481 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-08-31.
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…