renewal-risk

renewal-risk is a skill for Claude Code, Codex from quivly/skills. It costs 52 tokens per session (659 once invoked), scanned A, original, MIT.

A customer-success assessment of whether one account is likely to renew its contract in 60–90 days. It combines account health, product usage, billing, relationships, and contract terms.

In plain words
What is it for?
Use it to classify an account as safe, needing work, at risk, or likely to leave, and to decide what action remains before renewal.
Why use it?
It brings the warning signs into one decision before the contract's notice deadline passes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to classify an account as safe, needing work, at risk, or likely to leave, and to decide what action remains before renewal.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/quivly/skills/renewal-risk
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 quivly/skills --skill renewal-risk
Clone the repo
git clone --depth 1 https://github.com/quivly/skills

Made for: Claude Code, Codex.

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 renewal-risk

README.md
[![agentmods](https://agentmods.dev/badge/skills/quivly/skills/renewal-risk/github.svg)](https://agentmods.dev/skills/quivly/skills/renewal-risk)
Your own site
<a href="https://agentmods.dev/skills/quivly/skills/renewal-risk"><img src="https://agentmods.dev/badge/skills/quivly/skills/renewal-risk/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 renewal-risk

Your own site · 80×15
<a href="https://agentmods.dev/skills/quivly/skills/renewal-risk"><img src="https://agentmods.dev/badge/skills/quivly/skills/renewal-risk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 659 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.00052 $0.00659
Opus 5 $0.00026 $0.00329
Sonnet 5 $0.00010 $0.00132
Haiku 4.5 $0.00005 $0.00066

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

Security

Grade A, and why

renewal-risk 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-engineering/renewal-risk/SKILL.md · 45 lines

How it starts

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

Renewal Risk Read

You give a clear-eyed renewal read on one account: will they renew, what could change the answer, and what to do in the time remaining.

Core principle: the notice period is the real deadline — every date in the plan works backward from it.

Workflow

  1. Load the customer (get-customer) and contract terms (get-contracts, get-billing-subscription): renewal date, value, auto-renew clause, notice period — the notice period is the real deadline.
  2. Health trajectory (get-health-score, trend-analysis): direction over the last two quarters matters more than today's number.
  3. Usage trajectory (get-usage): growing, flat, or declining; seat utilization vs. what they pay for (under-utilization = downgrade pressure even when they renew).
  4. Relationship strength (get-contacts): is the champion still there, engaged, and senior enough? Single-threaded = elevated risk regardless of other signals.
  5. Weigh the four dimensions — value realization, usage trajectory, relationship strength, commercial posture — into a verdict.

Output Format

Renewal read: {Customer} — renewal date, notice deadline, ARR, verdict: Safe / Needs work / At risk / Likely churn

The four dimensions — one line each with evidence: value, usage, relationship, commercial

What could change the outcome — the 1-2 factors that most swing this renewal

Runway plan — what to do with the remaining weeks, in order: e.g., value recap deck → exec touch → commercial conversation. Include dates working back from the notice period.

Guidelines

  • Anchor every deadline to the notice period, not the renewal date.
  • Under-utilization deserves proactive right-sizing conversation over hoping they don't notice — the trust trade is worth it.
  • If verdict is "likely churn", shift the plan to save-attempt-or-graceful-exit; pretending otherwise wastes the runway.
  • Missing data on two or more of the four dimensions → don't force a verdict. Output "insufficient read" with the exact list of what to gather and where to get it.

Read the full file on GitHub · 45 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 · 45 lines · 52 tokens per session scan A 87ffdcbd7dde

Subscribe to this mod's changes

renewal-risk is a skill published in the GitHub repository quivly/skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 659 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

nitrostack-tools-resources-prompts

Guidelines and patterns for defining Tools, Resources, and Prompts in a NitroStack application with schema validation via Zod, including caching, rate-limiting, and base64 file uploads.

nitrocloudofficial/nitrostack · 48 tokens

prisma-postgres-setup

Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to "set up a database", "create a Prisma Postgres project", "get a connection string", "connect my app to Prisma Postgres", or "provision a database".

nitrocloudofficial/nitrostack · 67 tokens

nitrostack-middleware-pipeline

Best practices for implementing and applying Guards, Interceptors, Middleware, Pipes, and Exception Filters in the NitroStack SDK.

nitrocloudofficial/nitrostack · 32 tokens

nitrostack-ui-widgets

Best practices for linking tools to interactive frontend widgets using @Widget and @nitrostack/widgets SDK (including state sync, tool calling, display modes, media queries, and chat actions).

nitrocloudofficial/nitrostack · 44 tokens

prisma-cli

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, studio, validate, format, debug, and mcp. Use for ORM/database CLI workflows, not Prisma Compute app deployment. For Prisma Compute, @prisma/cli app deploy, compute:deploy, create-prisma --deploy, apps, deployments, logs, or domains, use the…

nitrocloudofficial/nitrostack · 125 tokens

nitrostack-mcp-app-architecture

Best practices and guidelines for bootstrapping, defining modules, using dependency injection, managing server lifecycles, and handling events in the NitroStack SDK.

nitrocloudofficial/nitrostack · 40 tokens