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/taizen-ai/taizen-claude-plugins/objections-prepnpx skills add taizen-ai/taizen-claude-plugins --skill objections-prepgit clone --depth 1 https://github.com/taizen-ai/taizen-claude-pluginsWrote 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/taizen-ai/taizen-claude-plugins/objections-prep)<a href="https://agentmods.dev/skills/taizen-ai/taizen-claude-plugins/objections-prep"><img src="https://agentmods.dev/badge/skills/taizen-ai/taizen-claude-plugins/objections-prep.svg" alt="Measured on agentmods" 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.00029 | $0.03283 |
| Opus 5 | $0.00015 | $0.01641 |
| Sonnet 5 | $0.00006 | $0.00657 |
| Haiku 4.5 | $0.00003 | $0.00328 |
Grade A, and why
objections-prep 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 6d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objections Prep Skill
Anticipate and prepare responses for common and deal-specific objections.
Purpose
Equip sales teams with confident, effective responses to objections that advance the deal rather than stall it.
Required Integrations
Setup: Connect these data sources to enable full functionality. Claude will prompt you to connect any missing integrations when you use this skill.
Data Sources
# OBJECTION HANDLING DATA SOURCES
# Configure the sources relevant to your objection preparation
# Enterprise Search (searches across all internal sources)
- source: enterprise_search
connector: "{{GLEAN | MOVEWORKS | ELASTIC}}"
data:
- internal_docs
- wiki_content
- shared_drives
- slack_history
# Call Recording & Objection Patterns
- source: call_recordings
connector: "{{GONG | CHORUS | CLARI}}"
data:
- objection_tracking
- successful_responses
- failed_responses
- objection_by_competitor
- objection_by_persona
- objection_by_deal_stage
# CRM Deal Data
- source: crm
connector: "{{SALESFORCE | HUBSPOT}}"
data:
- lost_deal_reasons
- stalled_deal_notes
- competitive_fields
- deal_stage_notes
# Competitive Intelligence
- source: competitive_intel
connector: "{{KLUE | CRAYON | KOMPYTE}}"
data:
- competitor_objections
- win_loss_by_competitor
- competitive_responses
- source: review_sites
sources:
- g2
- capterra
- trustradius
data:
- competitor_weaknesses
- our_criticisms
# Internal Knowledge
- source: internal_docs
connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION | CONFLUENCE}}"
paths:
- "/Sales Enablement/Objection Handling/"
- "/Sales/Battlecards/"
- "/Product/FAQ/"
- source: sales_content
connector: "{{SEISMIC | HIGHSPOT | SHOWPAD}}"
data:
- objection_handling_guides
- competitive_content
# Pricing & Packaging
- source: pricing_docs
connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION}}"
paths:
- "/Sales/Pricing/"
- "/Finance/Discount Guidelines/"
# Customer Proof Points
- source: customer_stories
connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION}}"
paths:
- "/Marketing/Case Studies/"
- "/Customer Success/Win Stories/"
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.
- 6d ago First seen · 496 lines · 29 tokens per session scan A d308b0857e69
objections-prep is a skill published in the GitHub repository taizen-ai/taizen-claude-plugins (8 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 3,283 once invoked, about $0.0001 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…