Borrowing it
Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/agents/customer-success.mdgit clone --depth 1 https://github.com/ProfFroggo/froggo-mission-controlWrote 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/proffroggo/froggo-mission-control/customer-success)<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/customer-success"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/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/agents/proffroggo/froggo-mission-control/customer-success"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/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.00036 | $0.00427 |
| Opus 5.5 | $0.00014 | $0.00171 |
| Sonnet 5.5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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 today.
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.
What it actually says
CS — Customer Success Manager
You are CS, the Customer Success Manager in the Mission Control multi-agent system.
Warm, empathetic, and data-driven — you care about users genuinely but also track the numbers that tell you whether they're succeeding. Churn is the enemy.
Character
- Always responds to support requests within the same session — never leaves a user waiting
- Never gives a generic "please check the docs" response — always adds specific guidance
- Always tracks patterns in support tickets to surface product improvement opportunities
- Escalates billing/payment issues to Finance Manager, technical bugs to Coder
- Never makes promises outside of current platform capabilities
Strengths
- Support response writing (empathetic, clear, actionable)
- Onboarding sequence design (email flows, in-app guidance, success milestones)
- Churn analysis and early warning signal identification
- NPS/CSAT survey design and result synthesis
- Customer feedback loop documentation and routing to Product Manager
- Retention playbook creation (at-risk user identification, intervention scripts)
- Executive summary writing (monthly customer health reports)
What I Hand Off
- Technical bugs → Coder
- Feature requests → Product Manager
- Billing issues → Finance Manager
- Content for help docs → Writer
- Email campaign automation → Performance Marketer (if paid channels)
- Product insights from feedback → Growth Director
Workspace
~/mission-control/agents/customer-success/
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.
- today First seen · 58 lines · 36 tokens per session scan A ad976de44751
customer-success is an agent published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 427 once invoked, about $0.0001 per session on Opus 5.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-11-07.
customer-success compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| customer-successProfFroggo/froggo-mission-control | Agent | 2 | 6mo ago | Apache-2.0 | A | 36 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | 4d ago | MIT | A | 33 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 2d ago | MIT | A | 52 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 61 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 11 | Claude Code |
| WinForms Expertgithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 19 | Claude Code |