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 agentmods add skills/alebgl77/claude-inc/objection-handlernpx skills add alebgl77/claude-inc --skill objection-handlergit clone --depth 1 https://github.com/alebgl77/claude-incWhat 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 | $0.00079 | $0.00659 |
| Opus 5 | $0.00039 | $0.00329 |
| Sonnet 5 | $0.00016 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
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 2d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Handler — Persuader
"An objection is a question wearing armor."
When to use
- "They said {objection} — how do I respond?"
- "Prospect ghosted after the proposal"
- "They're going with a competitor unless..."
- Paste the exact message or describe the moment; works for email replies and live-call scripting
Workflow
- Capture the objection verbatim — the words matter more than the summary.
- Diagnose the objection behind the objection: price usually means unclear value; "not now" means no burning pain or hidden stakeholder; "send me info" means unconvinced champion. State your diagnosis and confidence.
- Choose the frame: clarify (ask before answering), reframe (change the comparison), evidence (proof/case), trade (concede X for Y), or release (walk away with grace). Never argue.
- Script the response: acknowledge → explore with ONE question → respond to the real objection → propose a next step. ≤ 120 words for email, ≤ 4 lines for live.
- Prepare the branch: their 2 most likely replies to your response, and yours to each (one level deep only).
- Honesty check: if the objection is RIGHT (bad fit, real overprice, missing feature), say so and script the honest version — releasing a bad-fit deal is a win.
- Log it: append objection + what worked to an
objections-log.mdso patterns accumulate.
Output format
## Objection play — "{verbatim}"
Diagnosis: stated {X} → real {Y} (confidence: high/med/low)
Frame: {clarify/reframe/evidence/trade/release}
**Response ({channel})**: ...
**If they say** "{likely reply 1}" → ...
**If they say** "{likely reply 2}" → ...
**If the objection is simply true** → {honest path}
Next step to propose: ...
Quality bar
- Response opens with acknowledgment, not rebuttal
- Exactly one exploratory question before countering
- No pressure tactics, fake scarcity or manufactured urgency
- The "objection is true" path is genuinely considered
- Ends by proposing a concrete next step
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.
- 2d ago First seen · 53 lines · 79 tokens per session scan A c30769e40579
objection-handler is a skill published in the GitHub repository alebgl77/claude-inc (12 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 659 once invoked, about $0.0004 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-30.
Other skills, from other repositories
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad…
co-marketing
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership…
x-mastery-mentor
$10K/hr级X/Twitter运营导师。基于Nicolas Cole、Dickie Bush、Sahil Bloom、Justin Welsh、 Dan Koe、Alex Hormozi六位顶级创作者的方法论 + X开源算法深度分析 + AI/科技赛道专精策略， 提炼6个核心心智模型、10条决策启发式、完整的选题-写作-增长操作手册。 通用方法论为底座，AI/科技赛道为专精。 当用户提到「X运营」「推特」「Twitter」「怎么写推文」「怎么涨粉」「X策略」「推特选题」「tweet」「thread」「X算法」时使用。 即使用户只是说「这条推文怎么写」「帮我想个X内容」「推特增长」「发推」「write a tweet」「X…
geo-schema
Schema.org structured data audit and generation optimized for AI discoverability — detect, validate, and generate JSON-LD markup.
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.