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/gtmify/aigtm/objection-handlernpx skills add GTMify/aigtm --skill objection-handlergit clone --depth 1 https://github.com/GTMify/aigtmWhat 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.00095 | $0.01213 |
| Opus 5 | $0.00048 | $0.00607 |
| Sonnet 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 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 — 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.
- 2d ago First seen · 108 lines · 95 tokens per session scan A bff0a46cd802
objection-handler is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 24d ago), licensed MIT. It adds 95 tokens to every session and 1,213 once invoked, about $0.0005 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
gh-issue-to-demand-signal
Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's…
graphic-ebook
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a…
map-your-market
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences, then synthesizes everything into a positioning framework showing who your ICP is, what they say out loud, and exactly how…
company-radar
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
dependency-update-bot
Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated…
producthunt-launch-kit
Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.