linkedin-objection-handler

A writing aid for answering objections from potential customers on LinkedIn, a professional networking platform. It identifies concerns such as price, timing, trust, fit, or an existing solution, then drafts a reply.

In plain words
What is it for?
Use it when a LinkedIn reply contains an objection. Provide the prospect's message and your honest answer, and it returns a ready-to-send response.
Why use it?
It helps turn a prospect's pushback into a clear answer without avoiding the concern. It also keeps the conversation moving toward a possible call.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/styfinity/linkedin-engine/linkedin-objection-handler
Any agent
npx skills add styfinity/linkedin-engine --skill linkedin-objection-handler
Clone the repo
git clone --depth 1 https://github.com/styfinity/linkedin-engine

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 513 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.00513
Opus 5 $0.00026 $0.00257
Sonnet 5 $0.00010 $0.00103
Haiku 4.5 $0.00005 $0.00051

Measured yesterday against content hash d7b9820a203b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linkedin-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 yesterday.

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.

skills/linkedin-objection-handler/SKILL.md · 32 lines

What it actually says

LinkedIn Objection Handler

An objection is a question wearing a no. This skill answers it directly, reframes to the cost of staying still, and moves the thread one step toward a call.

Inputs

  • The objection as the prospect wrote it, plus your honest answer to it: $ARGUMENTS
  • The brief (offer, pains, proof, voice profile) loads automatically.

Do this

  1. Name the real concern underneath the words. Most objections are one of five: price, timing, trust, fit, or "we already do this". Say which one this is and why.
  2. Answer it first and directly. No dodging, no pivot before the answer lands. Use the operator's honest answer from the input as the spine.
  3. Reframe to the cost of the status quo. What does doing nothing keep costing them, in their own metric (leads, pipeline, hours, missed revenue)?
  4. Advance to a call. Offer a small, specific next step (a short call, a look at their numbers). Keep it conditional and low-pressure.
  5. Match the tone to the thread's warmth: cold gets shorter and lighter, warm can carry more substance.

Output

The reframe message, ready to paste, tier-matched to the thread's warmth. Then a one-line note stating the concern you actually addressed (price / timing / trust / fit / already-do-this).

Rules

  • Answer-first, always. Never evade the objection or change the subject before it is handled.
  • Never discount to win. Price objections get reframed against the cost of the status quo, not knocked down.
  • Advance to a call, do not hard-close in the text. Sending happens later, through the connected CLI/MCP layer, capped at 20 actions/day for new accounts.
  • Draft only. Claude drafts, the operator approves, and only then sends.
  • No em-dashes. Reads like a peer who respects the prospect's pushback.
  • If the reply has run hot and is ready to book, hand it to /linkedin-reply-triager. Run /linkedin-humanizer on the draft before sending.
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. yesterday First seen · 32 lines · 51 tokens per session scan A d7b9820a203b

Subscribe to this mod's changes

linkedin-objection-handler is a skill published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 513 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.

Related

Other skills, from other repositories

lemlist-campaign-from-icp

Use when the user says "create a lemlist campaign for X", "build a lemlist campaign from this ICP", "spin a lemlist campaign for Y", "ICP to lemlist", "natural language to lemlist campaign", "draft a lemlist campaign", "lemlist campaign for VPs/Managers/ICs at Z", or any variant indicating they want to turn a…

Othmane-Khadri/YALC-the-GTM-operating-system · 251 tokens

copywriting-ic-sequence

Writes a 3-email outbound sequence targeting Individual Contributors (SDR, AE, BDR, Account Manager, Marketing Specialist, Sales Rep, RevOps Analyst, CS Rep, etc.). Use this skill whenever the user wants to write cold emails for an IC, says "write me a sequence for SDRs", "draft emails targeting AEs", "emails for…

Othmane-Khadri/YALC-the-GTM-operating-system · 127 tokens

gtm-action-thinker

Brainstorms, challenges, and pushes any GTM idea to its fullest potential — on both the idea itself and its execution. Use this skill whenever the user shares a campaign idea, an outbound angle, a workflow concept, a positioning hypothesis, or any GTM initiative and wants to think it through deeply. Even if they just…

Othmane-Khadri/YALC-the-GTM-operating-system · 123 tokens

lost-deal-revival-agent

Drafts revival messages for closed-lost deals when a public company signal contradicts the original objection. Receives the signal-pair watcher's fire payload, fetches the verbatim Claap objection quote, and produces a 2-line draft that quotes it back. Default output is a HubSpot task for human review. Optional…

Othmane-Khadri/YALC-the-GTM-operating-system · 174 tokens

provider-builder

Use when a teammate wants to add a new vendor to YALC for an existing capability without shipping a release. Triggers include "add a new provider for X", "wire up [vendor] to YALC", "build an adapter for [vendor]", "I want to use [vendor] for [capability]", "add Apollo for icp-company-search", or any variant…

Othmane-Khadri/YALC-the-GTM-operating-system · 124 tokens

campaign-strategy

Pre-flight strategy advisor for a new campaign. Analyses every past campaign in the local YALC DB (HeyReach campaigns auto-sync on each run), their real outbound copy, where in the sequence each conversation first replied, every prior retro brief, and the validated/proven intelligence file. Then it proposes angle…

Othmane-Khadri/YALC-the-GTM-operating-system · 154 tokens