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 gs-bbluhm/gainsight-mcp-plugins --skill staircase-renewal-watchlistgit clone --depth 1 https://github.com/gs-bbluhm/gainsight-mcp-pluginsWrote 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/gs-bbluhm/gainsight-mcp-plugins/staircase-renewal-watchlist)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-renewal-watchlist"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-renewal-watchlist/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/gs-bbluhm/gainsight-mcp-plugins/staircase-renewal-watchlist"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-renewal-watchlist.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.00190 | $0.04152 |
| Opus 5.5 | $0.00076 | $0.01661 |
| Sonnet 5.5 | $0.00038 | $0.00830 |
| Haiku 4.5 | $0.00019 | $0.00415 |
Grade A, and why
staircase-renewal-watchlist 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 25d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staircase Renewal Command
Two jobs over one renewal window. For a CSM, it flight-plans the book: every renewal with the signals that decide it (risk, health, sentiment, expansion readiness, engagement, threading), ranked by where effort changes the outcome, each with a concrete play: defend, grow, or both. For a CS leader, it forecasts the window: renewals rolled up by segment into likely-renew / at-risk / churn-flagged revenue, so leadership sees the quarter's exposure and where to put the team. Both are report-first (renewal date, revenue, and analyst reads are structured fields) and churn-aware (a renewal already carrying a churn event is a forecast loss to manage, not a save to chase).
Which mode
- CSM planner (default when scoped to one owner): Steps 0-4 below, the ranked priority plan with per-account plays.
- Leader forecast (whole book / a tier / a team): the "Leader mode" section, the risk-weighted, churn-aware segment rollup. Run it first for the exec picture, then drop into the planner for any segment that needs account detail.
Foundation & portability (read first)
This is a workflow skill built on top of staircase-mcp-expert. That foundation owns the query mechanics (the EXISTS forms for insights/lifecycle events, child-aggregation group-by, the argument system, ../staircase-mcp-expert/references/query-patterns.md + ../staircase-mcp-expert/references/advanced-report-patterns.md, and the Priority-Weighting composite). This skill composes those primitives into the renewal workflow; it does not re-teach them. Always read the foundation before composing queries this session.
../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.- User profile:
~/.staircase-mcp/user-profile.mdholds the user's resolved scope. No scope → ask.
Portability law (this skill ships to any Staircase customer). Use ONLY standard Staircase primitives (the fields, insights, and lifecycle events every org has), never instance-specific _c custom fields and never a hardcoded account, owner, tier, or product name in logic. Segment names come from the org's own tier entity; owner ids from report_metadata. Discover before relying: call report_metadata and probe each insight/lifecycle-event type per org, since not all are enabled everywhere. If a signal is absent, degrade gracefully and say so; never fail because one insight or trend field is missing. Revenue: customer.revenue (contract) or customer.revenue_converted (corporate currency); both standard.
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.
- 25d ago First seen · 143 lines · 190 tokens per session scan A 38bfdb2dab7c
staircase-renewal-watchlist is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 190 tokens to every session and 4,152 once invoked, about $0.0008 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-09-26.
Other skills, from other repositories
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…