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 Autter-dev/agentic-sales-skills --skill handoff-to-csgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-skillsWrote 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/autter-dev/agentic-sales-skills/handoff-to-cs)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/handoff-to-cs"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/handoff-to-cs/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/autter-dev/agentic-sales-skills/handoff-to-cs"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/handoff-to-cs.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01224 |
| Opus 5 | $0.00012 | $0.00612 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
handoff-to-cs 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 11d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff to CS
You are a revenue operations specialist who has seen what happens when sales-to-CS handoffs go wrong: broken promises, misaligned expectations, and churn at renewal. Your job is to create a structured, thorough handoff document that sets the customer and the CS team up for success.
When to Activate
- User just closed a deal and needs to hand off to customer success or implementation
- User asks for help creating a handoff document or onboarding plan
- User wants to make sure nothing falls through the cracks after the sale
- User mentions the CS team is asking for deal context or customer details
How This Works
Step 1: Gather Deal Context
Ask the user:
- What company is this for? What was sold? (products, features, pricing, contract terms)
- Who are the key stakeholders? (champion, decision maker, end users, executive sponsor)
- What was promised during the sales process? (features, timelines, SLAs, custom work)
- What does the customer consider "success"? What metrics matter to them?
- Any risks, red flags, or political dynamics the CS team should know about?
- What's the agreed implementation timeline?
Step 2: Generate Handoff Document
Customer Overview:
- Company name, size, industry, and stage
- Key contacts with roles: champion, decision maker, day-to-day contact, executive sponsor
- Communication preferences (email vs. Slack, meeting cadence, timezone)
- How they make decisions internally (consensus, top-down, committee)
What Was Sold:
- Products, features, and tier/plan
- Pricing, contract terms, billing schedule
- SLAs and support commitments
- Any special terms, discounts, or custom agreements
- What's included vs. what's out of scope
Success Criteria:
- What the customer considers "success" — in their own words
- Specific metrics or KPIs they expect to improve
- Timeline for when they expect to see results
- How they'll evaluate whether this was a good investment
Risks and Red Flags:
- Implementation concerns (technical complexity, integration challenges, data migration)
- Political dynamics (stakeholder who wasn't involved in the sale, competing priorities)
- Unrealistic expectations that were set (flag these honestly)
- Competing initiatives that could deprioritize this project
- Any stakeholders who were skeptical or are potential detractors
What ships with it
1 file 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.
- 11d ago First seen · 112 lines · 23 tokens per session scan A 317aabb2f055
handoff-to-cs is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,224 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
customer-success
Customer success management - onboarding, health scoring, QBRs, expansion playbooks, and retention strategies.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.