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 swan-gtm/gtm-skills --skill customer-health-tiersgit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/customer-health-tiers)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/customer-health-tiers"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/customer-health-tiers/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/swan-gtm/gtm-skills/customer-health-tiers"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/customer-health-tiers.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.00156 | $0.02961 |
| Opus 5.5 | $0.00062 | $0.01184 |
| Sonnet 5.5 | $0.00031 | $0.00592 |
| Haiku 4.5 | $0.00016 | $0.00296 |
Grade A, and why
customer-health-tiers 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applies when you need to know, every day, which paying customers are slipping and which are outgrowing their plan, from what they actually do in the product. Produces three tiers per customer in the CRM, immediate alerts on changes that matter, and a weekly digest.
A single health score hides the thing you need to act on. A customer can be at high risk and high expansion at once: heavy usage concentrated in one person who is about to leave. So this skill keeps three independent reads, each with its own rules, and never blends them.
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full list and the defaults to tune.
{{USAGE_SOURCE}}: Where product usage lives (e.g. your product database or warehouse); read-only access is enough{{BILLING_SOURCE}}: Where subscriptions live: status, plan, price, first paid date, renewal date, included and used allowance, seats{{CRM}}: Your CRM (e.g. HubSpot, Salesforce){{USAGE_EVENT}}: The event that means "the product did work for them" (e.g. a workflow run, a report generated, an API call){{HUMAN_ACTION}}: The event that means "a person actively used it" (e.g. a user message, a login with an action){{KEY_SETUP_STEP}}: The setup step whose absence best predicts churn (e.g. connecting a sending account, installing the integration){{GENERATED_OUTPUT}}: Output the product produces for people to review, if any (e.g. drafts, alerts, recommendations){{USAGE_UNIT}}: The allowance customers consume (e.g. credits, seats, API calls){{PLAN_PRICING}}: Per-unit rate and base fee for the plans in the plan-upgrade check{{TOP_TIER_TAGS}}: Account tiers whose expansion goes to the dedicated owner (e.g. Diamond and Gold){{EXPANSION_OWNER}}: Owner of expansion for top-tier accounts{{CS_OWNER}}: Owner of risk alerts, and of expansion for everyone else{{EXPANSION_CHANNEL}}: Team channel that sees every high-expansion change{{EXPANSION_PIPELINE}}: The CRM pipeline and first stage for expansion deals{{DIGEST_RECIPIENT}}: Who gets the weekly digest
What ships with it
1 file 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 · 175 lines · 156 tokens per session scan A c90cb70b2141
customer-health-tiers is a skill published in the GitHub repository swan-gtm/gtm-skills (221 stars, last pushed 8d ago), licensed MIT. It adds 156 tokens to every session and 2,961 once invoked, about $0.0006 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-10-19.
Other skills, from other repositories
Pipedrive Automation
Automate Pipedrive CRM workflows including deal management, pipeline tracking, and sales reporting.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
icp-scoring
Score and tier ICP-fit accounts using firmographic, technographic, intent, pain, and timing signals. Produces a weighted ICP scorecard, tiering rules, anti-ICP exclusions, routing thresholds, and validation checklist. Use when defining target accounts, ranking TAM lists, prioritizing ABM accounts, or building fit…