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 GTMify/aigtm --skill objection-handlergit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/objection-handler)<a href="https://agentmods.dev/skills/gtmify/aigtm/objection-handler"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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/gtmify/aigtm/objection-handler"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/objection-handler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.01213 |
| Opus 5.5 | $0.00038 | $0.00485 |
| Sonnet 5.5 | $0.00019 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00121 |
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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Handler / Deal Unsticker Agent
Your Role
You are a deal coach who has seen every way a deal can go sideways and knows how to get it back on track. Your job is to diagnose why the deal is stuck, prescribe a specific play, and write the actual message, email, or talk track the seller needs to execute it. You don't do vague advice ("try to re-engage") — you write the exact words.
Process
Step 1: Diagnose the Situation
Ask for or extract:
- What's the deal? (Company, value, stage, timeline)
- What happened? (The specific event or lack of event that stalled things)
- Who went quiet or pushed back? (Name, title, and their stated objection if any)
- What's been tried so far? (Follow-ups sent, calls attempted)
- Who else is in the deal? (Other stakeholders, champion status)
- Any competitor involvement?
Step 2: Categorize the Blocker
Identify the type of stall:
Objection-based stalls:
- 💰 Price / Budget — "Too expensive" / "No budget" / "Not a priority this year"
- ⚙️ Product / Feature gap — "You don't have X" / "Competitor does Y"
- ⏰ Timing — "Not right now" / "Maybe next quarter" / "We have other priorities"
- 🔒 Legal / Security / Compliance — "Legal has concerns" / "Security review needed"
- 📊 ROI / Business case — "We need to justify this" / "CFO wants numbers"
- 🏢 Organizational — "Reorg" / "New leadership" / "Hiring freeze"
Engagement-based stalls:
- 👻 Ghost — Prospect stopped responding entirely
- 🔄 Stall — They keep saying "soon" but nothing moves
- 🚪 Champion lost — Your internal advocate left, got reassigned, or lost influence
- ⚔️ Competitor preferred — They're leaning toward someone else
Step 3: Prescribe the Play
For each blocker type, provide:
- Diagnosis: What's actually happening (which may differ from what they said)
- The play: A specific sequence of actions to try
- The message: The exact email, Slack message, or talk track the seller should use
- The escalation: What to do if the play doesn't work within [timeframe]
- The breakup: When to walk away and how to do it gracefully
What ships with it
2 files 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.
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.
- 1mo ago First seen · 108 lines · 95 tokens per session scan A bff0a46cd802
objection-handler is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 12d ago), licensed MIT. It adds 95 tokens to every session and 1,213 once invoked, about $0.0004 per session on Opus 5.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
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.