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 jeremylongworth-source/AgentSkills --skill customer-health-reviewgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/customer-health-review)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/customer-health-review"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/customer-health-review/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/jeremylongworth-source/agentskills/customer-health-review"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/customer-health-review.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.00461 |
| Opus 5 | $0.00036 | $0.00230 |
| Sonnet 5 | $0.00014 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
customer-health-review 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.
What it actually says
Customer Health Review
Core Workflow
- Identify the customer segment, lifecycle stage, owner, contract or renewal horizon, promised outcomes, and supplied account evidence.
- Review health signals across product usage, support history, stakeholder engagement, value realization, onboarding progress, renewal risk, and expansion or referral opportunity.
- Separate confirmed facts, missing data, assumptions, risks, and customer- facing claims.
- Turn the review into a practical account plan with next actions, owners, timing, evidence to gather, and escalation points.
- Draft QBR, renewal, or success-plan sections only from supplied evidence and mark all customer-facing content for review.
- Feed repeated account patterns back into product, support, revenue, and analytics workflows.
Safety Rules
- Draft-first and read-first by default.
- Do not invent usage, revenue, renewal terms, customer quotes, contract facts, product behavior, health scores, or support outcomes.
- Do not send customer messages, update CRM/account records, change terms, promise discounts, approve renewals, or make account changes without explicit approval.
- Escalate legal, security, billing, privacy, contract, incident, churn, strategic account, or executive-sponsor risks.
Deliverable Shape
- Account context and lifecycle stage
- Health signal summary
- Renewal, churn, adoption, and expansion risks
- Missing evidence and assumptions
- Customer value narrative
- Internal next-action plan
- Customer-facing QBR or success-plan draft, if requested
- Escalations and review gates
- Product, support, revenue, or analytics handoff notes
References
- Read
references/customer-health-review-checklist.mdwhen preparing account health reviews, QBR briefs, renewal plans, or customer success action plans.
What ships with it
2 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 · 52 lines · 71 tokens per session scan A 6fcc8af4e90e
customer-health-review is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 10d ago), licensed MIT. It adds 71 tokens to every session and 461 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
backend-specialist
A guide for designing and building backend services, the parts of an application that handle data, business rules, and requests. It covers APIs, databases, authentication, and service performance.
powersync
Best practices for building and maintaining applications with PowerSync: Cloud and self-hosted setup, sync configuration, client SDK usage, backend integration (Supabase, custom Postgres, MongoDB, Azure DocumentDB, MySQL, MSSQL), schema changes, watch and reactive queries (useQuery), attachments, the upload queue, and…
insforge
Use this skill when writing app code with InsForge or @insforge/sdk: database CRUD, auth, storage uploads/storage RLS, functions, OpenRouter AI, realtime, emails, Stripe or Razorpay payments, or pointing S3-compatible tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) at InsForge Storage. Trigger on requests like…
firebase-development
This skill should be used when working with Firebase projects, including initializing projects, adding Cloud Functions or Firestore collections, debugging emulator issues, or reviewing Firebase code. Triggers on "firebase", "firestore", "cloud functions", "emulator", "firebase auth", "deploy to firebase", "firestore…
python-database-patterns
SQLAlchemy and database patterns for Python. Triggers on: sqlalchemy, database, orm, migration, alembic, async database, connection pool, repository pattern, unit of work.
convex-expert
Convex backend specialist. Use this agent for any code inside a convex/ directory — function definitions, schemas, indexes, queries, mutations, actions, HTTP endpoints, cron jobs, file storage, auth wiring, and component installation. Knows the object-form function syntax, validator patterns, resource limits, and…