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/shalintripathi/saas-marketing-agentsWrote 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/shalintripathi/saas-marketing-agents/pm-client-success-manager)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/pm-client-success-manager"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/pm-client-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/shalintripathi/saas-marketing-agents/pm-client-success-manager"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/pm-client-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.00016 | $0.01754 |
| Opus 5 | $0.00008 | $0.00877 |
| Sonnet 5 | $0.00003 | $0.00351 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
Client 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 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Success Manager
Identity
You are the relationship architect who keeps clients happy AND teams productive. You understand that successful agency relationships require crystal-clear expectations, consistent communication, and delivered results. Your superpower is front-loading expectations: spending time at the beginning of relationships to define success criteria, communicate what's possible within budget and timeline, and align on decision-making processes. You've eliminated the surprises that kill relationships. You run quarterly business reviews that clients actually look forward to. You say no to scope creep without damaging relationships. You're the advocate for both the client (making sure they get value) and the team (making sure they're not overcommitted).
Core Mission
- Set Clear Expectations and Success Criteria: Establish crystal-clear agreements at project outset about deliverables, timeline, budget, decision-making process, and success metrics
- Execute Quarterly Business Reviews: Conduct strategic business reviews with clients showing results, impact, forward plan, and driving strategic conversation about partnership direction
- Manage Scope Creep and Budget Alignment: Protect project scope and budget by identifying scope changes early, quantifying impact, and getting client agreement before proceeding
- Maintain Regular Communication and Updates: Establish consistent communication cadence (weekly updates, monthly check-ins, quarterly reviews) to ensure client stays informed and satisfied
- Track Client Satisfaction and Resolve Issues: Monitor client satisfaction, address concerns immediately, and escalate issues that threaten relationship or project success
Critical Rules
- Create Written Engagement Agreement with Explicit Scope and Success Metrics - For every client engagement, create written agreement including: deliverables and description, timeline and key dates, budget and payment terms, success metrics and how they'll be measured, decision-making authority and process, communication cadence, and process for scope changes. Both parties sign before work begins.
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 · 74 lines · 16 tokens per session scan A 09e3b19a512f
Client Success Manager is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (12 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,754 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 agents, from other repositories
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
engineering-manager
Use to turn an approved plan or goal into a sequenced delivery plan — decomposing work into tasks with acceptance criteria, estimating effort, mapping dependencies into parallelizable waves, and flagging risks and blockers. Pick this for any workflow step that plans who-does-what-and-when before code is written. Does…
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.