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 mardab96/b2b-lead-generation-claude-skills --skill objection-cheat-sheetgit clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-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/mardab96/b2b-lead-generation-claude-skills/objection-cheat-sheet)<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/objection-cheat-sheet"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/objection-cheat-sheet/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/mardab96/b2b-lead-generation-claude-skills/objection-cheat-sheet"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/objection-cheat-sheet.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.00058 | $0.00975 |
| Opus 5 | $0.00029 | $0.00487 |
| Sonnet 5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
objection-cheat-sheet 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Cheat Sheet
Use this skill when
The same objections keep arriving and the answers are improvised every time.
Most objection handling advice is generic, which is why it does not work: it answers the objection as written rather than the one being made. "It is too expensive" is four different objections depending on who says it, and only your own lost deals can tell you which one you actually face.
This builds the sheet from your evidence, not from a framework.
Required input
At least one of:
- lost deal reasons from the CRM, with free text if it exists
- call notes or transcripts where objections came up
- email replies that declined, especially the longer ones
Better with:
- won deals where the same objection appeared and was overcome
- your pricing and what is included
- who the competitor usually is
- which stage each objection tends to land at
Analysis workflow
- Collect every objection instance verbatim before interpreting any of them. The exact words matter, because "we already have something" and "we just signed with someone" lead to opposite responses.
- Cluster them by what the buyer means rather than by what they said. Price objections in particular split into at least three: it costs more than the budget, it costs more than it is worth to me, and I cannot justify it internally.
- Count each cluster and note which stage it lands at. An objection that appears once is an anecdote; the sheet is for the ones that repeat.
- For each cluster, find the cases where it appeared and the deal still closed. That is where the real answer lives, and it usually is not what the sales deck says.
- Write the response as something a person would say out loud. If it needs to be read from a screen it will not be used on a call.
- Mark which objections are real disqualifiers. Some objections are correct, and the useful response is to agree and end the conversation rather than to handle it.
- Note what would change the objection upstream. Several of them are messaging problems that arrived late, not conversation problems.
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 · 87 lines · 58 tokens per session scan A 4edac1f69b65
objection-cheat-sheet is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 975 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
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…