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 varunk130/ai-gtm-skill-library --skill renewal-orchestrationgit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/renewal-orchestration)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/renewal-orchestration"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/renewal-orchestration/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/varunk130/ai-gtm-skill-library/renewal-orchestration"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/renewal-orchestration.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.00072 | $0.01400 |
| Opus 5.5 | $0.00029 | $0.00560 |
| Sonnet 5.5 | $0.00014 | $0.00280 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade A, and why
renewal-orchestration 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renewal Orchestration (RENEW Framework)
Design a renewal motion that produces forecastable Gross Revenue Retention, defends price, and uses the renewal moment as an expansion event - not a re-validation event. RENEW replaces "let's get the redline back" with a coordinated, signal-driven motion that starts 120+ days before contract end.
Core Principle
A renewal is won or lost 90 days before the contract end date, not in the redline cycle. RENEW front-loads risk identification and value evidence so the commercial conversation is short, defensible, and frequently expansion-oriented.
The RENEW Framework
| Letter | Stage | The Question |
|---|---|---|
| R | Risk Scoring | What is the renewal risk score 180 / 120 / 60 days out, and what signals drive it? |
| E | Engagement Re-establishment | Who is the buying group at renewal, and are they re-engaged? |
| N | Negotiation Posture | What is the price / terms posture, and what are the walk-away conditions? |
| E | Expansion Inclusion | What expansion play, if any, is bundled into the renewal conversation? |
| W | Win the Close | What artifact pack, decision criteria, and approval path are pre-aligned? |
Renewal Risk Scoring
Risk is a composite - not a single number. Score these at T-180:
| Dimension | Signal | Weight |
|---|---|---|
| Adoption | Engagement / workflow coverage vs. cohort | 25% |
| Outcome attainment | Customer's stated success metric progress | 25% |
| Stakeholder | Champion engaged in last 90 days, exec sponsor identified | 20% |
| Commercial signal | Procurement contact, late payment, MSA review | 15% |
| Competitive exposure | Inbound research on competitors, RFI signal | 10% |
| Support / quality | Critical-severity ticket trend | 5% |
Bucket into Green / Yellow / Red and route to the matching play.
Renewal Timeline
| Days Out | Activity | Owner |
|---|---|---|
| T-180 | Risk score baseline, success-plan refresh | CSM |
| T-150 | Stakeholder map refresh, exec sponsor re-engaged | CSM + AE |
| T-120 | Value-realization pack draft, expansion thesis identified | CSM + AE |
| T-90 | Renewal conversation initiated, EBR or value review | CSM + AE |
| T-60 | Commercial proposal, terms / pricing | AE + Deal Desk |
| T-30 | Negotiation + approvals | AE + Legal |
| T-0 | Signed renewal | All |
| T+30 | Renewal debrief, NRR / GRR booked, post-renewal plan | CSM |
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.
- 1mo ago First seen · 114 lines · 72 tokens per session scan A ae23d394f1ea
renewal-orchestration is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (7 stars, last pushed 10d ago), licensed MIT. It adds 72 tokens to every session and 1,400 once invoked, about $0.0003 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
internal-comms
Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience…
knowledge-ops
Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) — including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and…
procurement-optimizer
Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base — when the user needs a spend audit, spend categorization (UNSPSC-aligned with Pareto breakdown and industry profiles), purchasing-cycle analysis (bottleneck categories per Goldratt's Theory of Constraints), or…
capacity-planner
Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand…
chief-customer-officer-advisor
Chief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS…
company-os
The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks. Use when setting up company operations, selecting a management…