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/saolalab/clawforce/customer-successnpx skills add saolalab/clawforce --skill customer-successgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/customer-success)<a href="https://agentmods.dev/skills/saolalab/clawforce/customer-success"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/customer-success.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.00022 | $0.00730 |
| Opus 5 | $0.00011 | $0.00365 |
| Sonnet 5 | $0.00004 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
customer-success 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Success
Customer Lifecycle
Onboarding → Adoption → Expansion → Renewal
↑ |
└──────────── Churn Prevention ────┘
Health Score Framework
| Factor | Weight | Signals |
|---|---|---|
| Product Usage | 30% | DAU/MAU, feature adoption, API calls |
| Engagement | 25% | Support tickets, NPS responses, meetings |
| Business Value | 25% | ROI achieved, use cases deployed |
| Relationship | 20% | Executive sponsor, champion identified |
Health Levels
- Healthy (80-100): Active, expanding, advocate potential
- Neutral (50-79): Using product but not growing
- At Risk (0-49): Declining usage, negative sentiment, churn risk
Onboarding Playbook
Week 1: Foundation
- Welcome call / kickoff meeting
- Account setup verification
- Key stakeholder identification
- Success criteria definition
- Training schedule set
Week 2-4: Activation
- Core feature training
- First use case deployed
- Initial value demonstrated
- Feedback collection
- Quick wins documented
Month 2-3: Adoption
- Advanced feature training
- Additional use cases
- Best practices shared
- Success metrics baseline
- Executive business review
Churn Prevention
Early Warning Signs
- Usage decline — DAU/MAU dropping
- Support spikes — More tickets, more frustration
- Silence — No engagement, no responses
- Champion changes — Key contact leaves
- Competitor mentions — Evaluating alternatives
Intervention Playbook
- Acknowledge — Reach out proactively
- Listen — Understand the real issues
- Act — Provide immediate value or fix
- Follow up — Ensure resolution stuck
- Document — Log learnings for prevention
QBR Template
Quarterly Business Review Agenda
- Business Outcomes (15 min)
- ROI achieved this quarter
- Success metrics vs goals
- Customer wins/testimonials
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 · 111 lines · 22 tokens per session scan A 46240fa1a9b7
customer-success is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 730 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-30.
Other skills, from other repositories
agenticmail
🎀 AgenticMail — Full email, SMS, storage & multi-agent coordination for AI agents. 63 tools.
ai-meeting-scheduling
Booking links fail for groups. SkipUp schedules meetings with 2-50 participants via email — one API call coordinates across timezones automatically. Also: check status, pause, resume, or cancel requests. Async only — does not instant-book, access calendars, or do free/busy lookups.
agentic-paper-digest-skill
Fetches and summarizes recent arXiv and Hugging Face papers with Agentic Paper Digest. Use when the user wants a paper digest, a JSON feed of recent papers, or to run the arXiv/HF pipeline.
eachlabs-voice-audio
Text-to-speech, speech-to-text, voice conversion, and audio processing using EachLabs AI models. Supports ElevenLabs TTS, Whisper transcription with diarization, and RVC voice conversion. Use when the user needs TTS, transcription, or voice conversion.
academic-literature-search
这是一个专注于学术文献检索的专业工具，集成了多个权威学术数据库，提供全面、快速、准确的文献检索服务。支持多数据库并发检索、高级过滤、智能排序和多种输出格式。.
03_task6
整合多部门 Slack 消息，交叉核对数据，识别依赖关系与风险，为高管起草董事会级别的执行摘要草稿。适用场景：跨部门项目状态汇总、董事会会议准备、需要数据对账和风险识别的高管报告。.