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-account-deep-divegit 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-account-deep-dive)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-account-deep-dive"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-account-deep-dive/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-account-deep-dive"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-account-deep-dive.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.00111 | $0.01450 |
| Opus 5.5 | $0.00044 | $0.00580 |
| Sonnet 5.5 | $0.00022 | $0.00290 |
| Haiku 4.5 | $0.00011 | $0.00145 |
Grade A, and why
staircase-account-deep-dive 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staircase Account Deep Dive
The "catch me up" workflow. One account, the last ~90 days of communication, synthesized into something you can read in two minutes and act on today. This is the default account read when someone just needs to know where things stand.
Foundation references
Read these before composing the query if you have not in this session:
../staircase-mcp-expert/: query mechanics, field catalog, non-determinism handling, analyst data models.../../_shared/staircase-output-best-practices.md: the house style every artifact follows.
When to use
Trigger phrases:
- "catch me up on [account]"
- "what's going on with [account]"
- "give me the latest on [account]"
- "deep dive on [account]" / "brief me on [account]"
- "where do we stand with [account]"
Optimized for: Cowork (card + sections) and Code (markdown + optional file). This is the single most reliable Staircase surface, so it is the safest default.
Step 1: Resolve the account
Call staircase_account_lookup(name=<account>) first to get an account_id.
- High-confidence single match: proceed.
- Multiple low-confidence matches: STOP and ask the user which account they mean. Do not guess.
- No match: tell the user plainly and ask for an alternate spelling or the parent company name.
Step 1.5: Pull the structured scaffold (cheap, deterministic)
Call staircase_account_info(account_id) once before the narrative. It returns, in one deterministic call: health / sentiment / engagement scores, risk level, expansion readiness + summary, renewal date, revenue (+ per-product ARR where synced), tier, journey phase, last engagement / last touch, owner, and the stored analyst summaries (AI Summary, Churn Risk, Renewal). Use it to set the status line and health framing on real numbers and to decide what the catch-up should emphasize. Then analyze_account supplies the dated developments, open threads, sentiment trend, and evidence the scores alone can't tell you. (If the user only wants the fast factual snapshot, account_info may be enough on its own.)
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 · 114 lines · 111 tokens per session scan A f1043cfe56e7
staircase-account-deep-dive is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 111 tokens to every session and 1,450 once invoked, about $0.0004 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…