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-risk-radargit 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-risk-radar)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-risk-radar"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-risk-radar/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-risk-radar"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-risk-radar.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.00149 | $0.04616 |
| Opus 5.5 | $0.00060 | $0.01846 |
| Sonnet 5.5 | $0.00030 | $0.00923 |
| Haiku 4.5 | $0.00015 | $0.00462 |
Grade A, and why
staircase-risk-radar 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staircase Risk Radar (leader / portfolio)
A CS leader does not need a red list of hundreds of accounts. They need four answers: how much revenue is at risk, why, which of it has a clock on it, and what to do, segmented so they can point a team at it. This skill answers those from structured reports (deterministic ranking, counts, revenue rollups), then grounds the "why" in the Risk analyst's stored driving factors and the cohort's own communication themes.
This is the portfolio lens. For a single account's full risk read + save sequence use ../staircase-risk-check/; for one CSM's weekly action list across every motion use the Book Triage skill. This skill deliberately stops at the leader's decisions: where to invest, which program to stand up, which deals to personally step into.
Foundation references (read BEFORE composing any query)
../staircase-mcp-expert/and../staircase-mcp-expert/references/advanced-report-patterns.md: the report engine, the EXISTS/child-aggregation forms, the argument system, field ids, and the reliability rules in../staircase-mcp-expert/references/anti-patterns.md. This skill assumes them.../staircase-app-design/: the app chrome + the interactive-experiences standard the radar follows. Read before rendering the visual.../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.
Scope (decide first)
- Whole org (default for a leader): status = Active, no owner filter.
- A segment: add
customer.tierIn [...] (tier names via thetierentity; they vary per org, so discover them rather than assuming). - A team, by book owner:
customer.owneris not always the CSM; on some orgs it holds a structurally different role, and attributing risk "by owner" then routes the finding to the wrong people. Use the resolved book-owner field (scope.book_owner_fieldin the profile, or the foundation's first-call contract), then filtercustomer.<book_owner_field> In [<user_ids>](ids fromcurrent_user_idor auserroster report) orcustomer.<book_owner_field>.full_name In ["<names>"]. - Portable fields only. Never hardcode a specific
_cfield id (e.g. a custom ARR field). Usecustomer.revenue_convertedfor revenue,tier.namefor segment, and the confirmed book-owner field (a runtime parameter) for team rollups. Discover what exists per org viareport_metadata.
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.
- 25d ago First seen · 158 lines · 149 tokens per session scan A 62c4072cc4bf
staircase-risk-radar is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 149 tokens to every session and 4,616 once invoked, about $0.0006 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…