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 jbalbu01/sales-enablement-plugin --skill handoff-buildergit clone --depth 1 https://github.com/jbalbu01/sales-enablement-pluginWrote 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/jbalbu01/sales-enablement-plugin/handoff-builder)<a href="https://agentmods.dev/skills/jbalbu01/sales-enablement-plugin/handoff-builder"><img src="https://agentmods.dev/badge/skills/jbalbu01/sales-enablement-plugin/handoff-builder.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.00129 | $0.02782 |
| Opus 5 | $0.00064 | $0.01391 |
| Sonnet 5 | $0.00026 | $0.00556 |
| Haiku 4.5 | $0.00013 | $0.00278 |
Grade A, and why
handoff-builder 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 8d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Builder
Create seamless transitions between GTM functions. The handoff between sales and CS is where most customer relationships break — the customer repeats everything they already told sales, expectations get lost, and trust erodes. This skill prevents that.
The Handoff Problem
Every GTM handoff is a moment of risk:
- SDR → AE: Context about the prospect's pain and urgency gets lost
- AE → SE: Technical requirements aren't fully communicated
- Sales → CS: Customer expectations don't match what was sold
- Sales → Implementation: Scope and timeline assumptions differ
- CS → Sales: Expansion opportunities don't get pursued
Bad handoffs cost deals, create churn, and destroy cross-functional trust.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ HANDOFF BUILDER │
├─────────────────────────────────────────────────────────────────┤
│ HANDOFF TYPES │
│ 1. SDR → AE — Lead context and qualification notes │
│ 2. Sales → CS — Full deal context and customer expectations │
│ 3. AE → SE — Technical requirements for demo/POC │
│ 4. Sales → Implementation — Scope, timeline, requirements │
│ 5. CS → Sales — Expansion signals and customer context │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Full deal data, contacts, company, and notes │
│ + ~~CRM: Deal timeline and stage progression history │
│ + ~~CRM: Associated contacts with roles and titles │
│ + ~~conversation intelligence (Gong): Key call transcripts │
│ + ~~conversation intelligence (Gong): Discovery insights │
│ + ~~conversation intelligence (Gong): Objections raised │
│ + ~~data enrichment (ZoomInfo): Company and contact profiles │
│ + ~~data enrichment (LinkedIn): Stakeholder backgrounds │
│ + ~~chat: Internal deal discussions and context │
│ + ~~calendar/email: Meeting history and correspondence │
└─────────────────────────────────────────────────────────────────┘
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.
- 8d ago First seen · 283 lines · 129 tokens per session scan A 0a2f6e927521
handoff-builder is a skill published in the GitHub repository jbalbu01/sales-enablement-plugin (14 stars, last pushed 6mo ago), licensed MIT. It adds 129 tokens to every session and 2,782 once invoked, about $0.0006 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
linkedin-campaign-complete
Complete LinkedIn campaign guide - targeting strategy, copywriting rules, human-like campaign steps, and message templates. Use when building LinkedIn outreach sequences, writing LinkedIn messages, or planning multi-touch campaigns.
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
head-of-pmo
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
chief-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…