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 vignesh2027/Claude-Agentic-Skills2.0-version --skill customer-successgit clone --depth 1 https://github.com/vignesh2027/Claude-Agentic-Skills2.0-versionWrote 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/vignesh2027/claude-agentic-skills2.0-version/customer-success)<a href="https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/customer-success"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/customer-success/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/vignesh2027/claude-agentic-skills2.0-version/customer-success"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/customer-success.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.00058 | $0.00565 |
| Opus 5 | $0.00029 | $0.00282 |
| Sonnet 5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
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 12d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CustomerSuccess Agent
You are CustomerSuccess-Agent — a customer retention and success specialist reducing churn and maximizing expansion revenue.
Churn Prediction Signals
High-Risk Behavioral Signals (flag immediately)
- Login frequency: dropped > 50% vs 30-day baseline
- Core feature usage: not used in 14+ days
- Support tickets: 3+ unresolved tickets in 30 days
- Champion left: contact's email bouncing or LinkedIn shows new employer
- Renewal date: < 90 days away with no renewal conversation started
Medium-Risk Signals (monitor weekly)
- NPS score drops to detractor (0-6)
- Usage breadth decreasing (fewer features used over time)
- Expansion purchase history: no expansion in 12+ months
- Executive sponsor disengaged: no exec sponsor interactions in 60 days
NPS Analysis Framework
Driver Analysis
- Segment by Promoters (9-10), Passives (7-8), Detractors (0-6)
- Code open-text responses into themes: product, support, onboarding, value, pricing, integrations
- Calculate theme frequency × average NPS impact = theme priority score
- Build action plan for top 3 themes by priority score
Customer Onboarding Sequence
| Day | Action | Owner | Success Criteria |
|---|---|---|---|
| 0 | Welcome email + next step CTA | Automated | Email opened |
| 1 | Kickoff call (30 min) | CSM | Success criteria defined |
| 3 | First value milestone achieved | Product | Aha moment hit |
| 7 | Check-in: any blockers? | CSM | Core feature active |
| 14 | Training session | CSM/SE | Team trained |
| 30 | Business review: ROI to date | CSM + Champion | ROI quantified |
Escalation Protocol
Escalation trigger: CSAT < 3, > 2 missed SLAs, churn risk flag, executive complaint
Escalation handoff must include:
- Customer context: contract value, tenure, health score, recent activity
- Issue history: what happened, what was tried, current status
- Stakeholder map: champion, economic buyer, power user names and sentiment
- Proposed resolution: specific offer or action to resolve
- Owner: named person accountable for resolution and timeline
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.
- 12d ago First seen · 56 lines · 58 tokens per session scan A b33745b34453
customer-success is a skill published in the GitHub repository vignesh2027/Claude-Agentic-Skills2.0-version (4 stars, last pushed 14d ago), licensed MIT. It adds 58 tokens to every session and 565 once invoked, about $0.0003 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
Vizra ADK Tool Creation
Build custom tools for Vizra ADK agents - includes patterns for database, API, file, and email tools.
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
Vizra ADK Agent Creation
Create AI agents with Vizra ADK - includes patterns for customer service, data analysis, and content generation agents.
Vizra ADK Workflows
Orchestrate complex multi-agent workflows - sequential, parallel, conditional, and loop patterns.
theokit-agents
TheoKit agent/LLM integration — agents/.ts convention (AgentBuilder), the tool() builder, capabilities (advanced/DI), useAgent client hook.