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 omer-metin/skills-for-antigravity --skill customer-successgit clone --depth 1 https://github.com/omer-metin/skills-for-antigravityWrote 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/omer-metin/skills-for-antigravity/customer-success)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/customer-success"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/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/omer-metin/skills-for-antigravity/customer-success"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/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.00077 | $0.00673 |
| Opus 5 | $0.00039 | $0.00336 |
| Sonnet 5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00067 |
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 9d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Success
Identity
Principles
- {'name': 'Time to value is everything', 'description': 'The faster users get value, the more likely they stick. Measure and\noptimize time to first value moment. Remove every obstacle between\nsignup and aha moment.\n', 'examples': {'good': 'User sees value in first session, under 5 minutes', 'bad': 'Value requires days of setup, learning, configuration'}}
- {'name': 'Proactive beats reactive', 'description': 'Reach out before problems escalate. Health scores predict churn before\nit happens. Intervention when metrics dip is worth 10x intervention\nafter cancellation request.\n', 'examples': {'good': 'Alert when usage drops, proactive check-in call', 'bad': 'Notice churn only when credit card fails'}}
- {'name': 'Segment for relevance', 'description': 'Not all customers are the same. High-touch for enterprise, tech-touch\nfor SMB, self-serve for individuals. Match effort to customer value\nand needs.\n', 'examples': {'good': 'Dedicated CSM for enterprise, automated sequences for self-serve', 'bad': 'Same email blast to everyone regardless of tier'}}
- {'name': 'Measure leading indicators', 'description': 'Revenue is a lagging indicator. By the time it drops, damage is done.\nTrack leading indicators: engagement, feature adoption, support tickets,\nNPS changes.\n', 'examples': {'good': 'Dashboard with daily engagement, weekly feature adoption, monthly NPS', 'bad': 'Only looking at MRR and wondering why it dropped'}}
- {'name': 'Make expansion natural', 'description': 'Upselling should feel like helping, not selling. When customers outgrow\ntheir tier, expansion is a solution. When they hit limits, upgrade is\nobvious.\n', 'examples': {'good': 'Usage-based nudge when approaching limits with clear value prop', 'bad': 'Aggressive sales calls pushing features they do not need'}}
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
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.
- 9d ago First seen · 29 lines · 77 tokens per session scan A 0ca5b54f0c97
customer-success is a skill published in the GitHub repository omer-metin/skills-for-antigravity (145 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 673 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
test-driven-development
Drives development with tests via Red-Green-Refactor and the Prove-It pattern, with hard rules against weakening assertions or faking green suites. Use when implementing any logic, fixing any bug, or changing any behavior. Triggers on "add a feature", "fix this bug", "write tests", or any task where done must be…
ai-ops
Guides operational excellence for AI/ML systems in production. Use when deploying models, managing inference infrastructure, monitoring model drift, or maintaining AI-powered features. Use when you need reliable, observable, and governable machine learning systems.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
data-engineering
Guides data pipeline design, ETL/ELT workflows, schema evolution, and data quality assurance. Use when building data pipelines, designing data warehouses, migrating schemas, or ensuring data integrity across systems. Use when you need reliable, testable, and observable data flows.
debugging-and-error-recovery
Guides systematic root-cause debugging with hard rules against guess-fixes and symptom suppression. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Triggers on "this is broken", "tests are failing", "why doesn't this work", or any error output.