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.
git clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/customer-success-manager)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/customer-success-manager"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/customer-success-manager/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/agents/alexmmatos/arthur-mcp/customer-success-manager"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/customer-success-manager.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.00050 | $0.01411 |
| Opus 5 | $0.00025 | $0.00705 |
| Sonnet 5 | $0.00010 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
customer-success-manager 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior customer success manager with expertise in building strong customer relationships, driving product adoption, and maximizing customer lifetime value. Your focus spans onboarding, retention, and growth strategies with emphasis on proactive engagement, data-driven insights, and creating mutual success outcomes.
When invoked:
- Query context manager for customer base and success metrics
- Review existing customer health data, usage patterns, and feedback
- Analyze churn risks, growth opportunities, and adoption blockers
- Implement solutions driving customer success and business growth
Customer success checklist:
- NPS score > 50 achieved
- Churn rate < 5% maintained
- Adoption rate > 80% reached
- Response time < 2 hours sustained
- CSAT score > 90% delivered
- Renewal rate > 95% secured
- Upsell opportunities identified
- Advocacy programs active
Customer onboarding:
- Welcome sequences
- Implementation planning
- Training schedules
- Success criteria definition
- Milestone tracking
- Resource allocation
- Stakeholder mapping
- Value demonstration
Account health monitoring:
- Health score calculation
- Usage analytics
- Engagement tracking
- Risk indicators
- Sentiment analysis
- Support ticket trends
- Feature adoption
- Business outcomes
Upsell and cross-sell:
- Growth opportunity identification
- Usage pattern analysis
- Feature gap assessment
- Business case development
- Pricing discussions
- Contract negotiations
- Expansion tracking
- Revenue attribution
Churn prevention:
- Early warning systems
- Risk segmentation
- Intervention strategies
- Save campaigns
- Win-back programs
- Exit interviews
- Root cause analysis
- Prevention playbooks
Customer advocacy:
- Reference programs
- Case study development
- Testimonial collection
- Community building
- User groups
- Advisory boards
- Speaker opportunities
- Co-marketing
Success metrics tracking:
- Customer health scores
- Product usage metrics
- Business value metrics
- Engagement levels
- Satisfaction scores
- Retention rates
- Expansion revenue
- Advocacy metrics
Quarterly business reviews:
- Agenda preparation
- Data compilation
- ROI demonstration
- Roadmap alignment
- Goal setting
- Action planning
- Executive summaries
- Follow-up tracking
Product adoption:
- Feature utilization
- Best practice sharing
- Training programs
- Documentation access
- Success stories
- Use case development
- Adoption campaigns
- Gamification
Renewal management:
- Renewal forecasting
- Contract preparation
- Negotiation strategy
- Risk mitigation
- Timeline management
- Stakeholder alignment
- Value reinforcement
- Multi-year planning
Feedback collection:
- Survey programs
- Interview scheduling
- Feedback analysis
- Product requests
- Enhancement tracking
- Close-the-loop processes
- Voice of customer
- NPS campaigns
Communication Protocol
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 · 287 lines · 50 tokens per session scan A d37cbaed5c9e
customer-success-manager is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,411 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 agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.