health-score-builder

health-score-builder is a skill for Claude Code from bjorn-ingmanson/thefroject-plugins. It costs 50 tokens per session (1,205 once invoked), scanned A, original, MIT.

A customer health scoring model that combines usage, support, engagement, financial, and relationship information into a score for each customer.

In plain words
What is it for?
Use it to create or refine a scoring framework, or assess a specific customer. It uses product activity, support history, meetings, stakeholder involvement, contract and payment data, and customer segments.
Why use it?
It turns scattered customer signals into a consistent way to spot accounts that may be at risk or ready for further attention.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the thefroject-customer-success plugin — 47 skills, 11 commands shipped together

Good fit Use it to create or refine a scoring framework, or assess a specific customer. It uses product activity, support history, meetings, stakeholder involvement, contract and payment data, and customer segments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bjorn-ingmanson/thefroject-plugins/health-score-builder
Install

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.

Any agent
npx skills add bjorn-ingmanson/thefroject-plugins --skill health-score-builder
Clone the repo
git clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-plugins

Made for: Claude Code.

Or install thefroject-customer-success, the plugin that ships this one along with the rest of its 47 skills, 11 commands.

Wrote 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.

agentmods badge for health-score-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/health-score-builder/github.svg)](https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/health-score-builder)
Your own site
<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/health-score-builder"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/health-score-builder/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.

agentmods 80×15 button for health-score-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/health-score-builder"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/health-score-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,205 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01205
Opus 5 $0.00025 $0.00602
Sonnet 5 $0.00010 $0.00241
Haiku 4.5 $0.00005 $0.00120

Measured 10d ago against content hash a942dca78261, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

health-score-builder 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 10d 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.

customer-success/skills/health-score-builder/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Health Score Builder

Create a quantitative health score that turns scattered signals into a single actionable number per customer.

Input Required

  1. Customer data — usage metrics, support tickets, engagement history (check context/current-data.md)
  2. Product data — feature adoption, login frequency, key actions
  3. Financial data — contract value, payment history, expansion/contraction
  4. Relationship data — stakeholder engagement, NPS/CSAT responses, meeting cadence
  5. Segment definitions — how customers are grouped (size, industry, tier)

Model Design

Step 1 — Define Health Dimensions

Score each dimension independently, then combine:

Dimension Weight Signals Why It Matters
Product Adoption 30% DAU/MAU, feature usage, depth of use Customers who use the product stay
Support Health 20% Ticket volume, severity, resolution time, sentiment Rising tickets = rising frustration
Engagement 20% Meeting attendance, email responsiveness, champion activity Engaged customers renew
Financial 15% Payment on time, contract growth, upsell conversations Money signals commitment
Relationship 15% Stakeholder map depth, NPS score, executive access Strong relationships survive problems

Adjust weights based on your product and sales motion. Usage-heavy products should weight adoption higher. Service-heavy businesses should weight engagement higher.

Step 2 — Define Scoring Criteria Per Dimension

Product Adoption (0-100):

Score Range Criteria
80-100 Using core features weekly, adopted 3+ modules, growing usage
60-79 Using core features, but shallow. 1-2 modules only
40-59 Sporadic usage, declining trend, limited feature adoption
20-39 Minimal usage, only 1-2 users active, no growth
0-19 No meaningful usage in the past 30 days

Support Health (0-100):

Read the full file on GitHub · 123 lines

Changes

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.

  1. 10d ago First seen · 123 lines · 50 tokens per session scan A a942dca78261

Subscribe to this mod's changes

health-score-builder is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 1,205 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens