Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zime-ai/zime-gtm-skillsnpx agentmods add skills/zime-ai/zime-gtm-skills/customer-successWrote 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/zime-ai/zime-gtm-skills/customer-success)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/customer-success"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/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/zime-ai/zime-gtm-skills/customer-success"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/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.00071 | $0.00850 |
| Opus 5 | $0.00036 | $0.00425 |
| Sonnet 5 | $0.00014 | $0.00170 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade C, and why
customer-success scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
it touches — don't refuse the audit over the label. How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Customer Success Audit
You are a customer-success health-review auditor. Your goal is to tell a CSM whether a routine QBR was substantive, or just a status-update formality.
Audits a periodic account health review (QBR or similar) against eight
dimensions. This is a broader, ongoing-relationship lens — distinct from
churn-prevention (triggered by risk signals) and
upsell-expansion (triggered by an opportunity). Use this one for the
regular check-in that happens regardless of whether anything's currently
wrong or expanding. Runs entirely on the file you give it — no network
calls, no credentials, nothing leaves your machine.
When to use this
- A CSM is prepping for or reviewing a QBR and wants a structured read.
- A CS lead wants to spot-check whether periodic reviews are substantive or just a status-update formality.
- RevOps wants to sweep for accounts overdue for a health review.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass — don't stop to ask which call or whether a borderline quote counts.
- If the call is clearly risk- or opportunity-triggered rather than a routine review, say so in one line and still score whichever dimensions it touches — don't refuse the audit over the label.
- If the file is truncated or a section is inaudible, score what's there and mark the affected dimensions Unclear rather than guessing.
Modes
Dispatch on the input file's extension.
Transcript mode (.txt, .vtt, .json, .md)
claude "run customer-success on ./calls/acme-qbr.txt"
Score against references/rubric.md. Per dimension: Status
(Covered/Partial/Missed), Evidence (quote/timestamp, or Unclear
rather than guess), Note if not fully covered.
Close with a one-line overall account read and the single most useful follow-up action. Run the reads-well-too check first.
CSV mode (.csv)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 96 lines · 71 tokens per session scan C 35adf01b44ce
customer-success is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 71 tokens to every session and 850 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
audit-swan
Checks whether a Swan workspace is structurally healthy. Use for configuration audits that surface missing knowledge, disconnected integrations, exhausted senders, broken triggers, sparse CRM data, and credit or subscription issues.
handle-demo-request
Use this skill when someone requests a demo through your website — a "Book a demo" form, a webhook carrying little more than a work email — and the question is what happens in the next sixty seconds. Enriches the person and company, decides fit and buyer persona separately, and routes the request down one of three…
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…
cargo-workspace-management
Administer a Cargo workspace and talk back to the Cargo team — invite and manage members, mint and rotate API tokens, organize plays, tools, and agents into folders, inspect roles, upload batch input files, and file reports. Triggers: "invite my teammate", "create an API token for CI", "who has access", "organize…
linkedin-prospecting-loop
End-to-end LinkedIn prospecting loop that turns an ICP into a qualified, signal-prioritized, personalized, sequenced outbound run by orchestrating existing skills + MCPs (Apify find, Apollo enrich, lead-scoring, cold-DM doctrine, Extrovert voice) behind a human approval gate at every phase. Triggers: "LinkedIn…