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 quivly/skills --skill renewal-riskgit clone --depth 1 https://github.com/quivly/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/quivly/skills/renewal-risk)<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.
<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>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.00052 | $0.00659 |
| Opus 5.5 | $0.00021 | $0.00264 |
| Sonnet 5.5 | $0.00010 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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 2mo 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 — 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
- 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. - Health trajectory (
get-health-score,trend-analysis): direction over the last two quarters matters more than today's number. - Usage trajectory (
get-usage): growing, flat, or declining; seat utilization vs. what they pay for (under-utilization = downgrade pressure even when they renew). - Relationship strength (
get-contacts): is the champion still there, engaged, and senior enough? Single-threaded = elevated risk regardless of other signals. - 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.
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.
- 2mo ago First seen · 45 lines · 52 tokens per session scan A 87ffdcbd7dde
renewal-risk is a skill published in the GitHub repository quivly/skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 659 once invoked, about $0.0002 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-08-31.
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.
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".
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).
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".
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.
nitrostack-middleware-pipeline
Best practices for implementing and applying Guards, Interceptors, Middleware, Pipes, and Exception Filters in the NitroStack SDK.