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-voice-of-customergit 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-voice-of-customer)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-voice-of-customer"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-voice-of-customer/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-voice-of-customer"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-voice-of-customer.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.00155 | $0.02375 |
| Opus 5.5 | $0.00062 | $0.00950 |
| Sonnet 5.5 | $0.00031 | $0.00475 |
| Haiku 4.5 | $0.00015 | $0.00237 |
Grade A, and why
staircase-voice-of-customer 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staircase Voice of Customer (cohort intelligence)
What are customers saying, as a measured profile, not a vibe. This is the capability a CRM cannot replicate: a topic / sentiment / volume / trend profile for any cohort × window × channel, drilled from the big theme down to the specific reason, and anchored in the customers' own words. The engine is the parent_topic entity (deterministic counts, sentiment, and period-over-period trend), the child-topic drill (semantic_search topic channel), and evidence quotes.
Foundation & portability (read first)
A workflow skill on top of staircase-mcp-expert. That foundation owns the query mechanics (the parent_topic cohort-scoping via the filter.customer argument, the VoC drill in ../staircase-mcp-expert/references/advanced-report-patterns.md, the argument system). This skill composes them into the VoC workflow. Read it before composing queries.
../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.- Portability: standard primitives only: the canonical parent topics every Staircase org has (Support & issues, Commercial & contracts, Feature requests, Implementation & projects, Risk & dissatisfaction, Customer success & relations, Security & compliance, Organizational changes, Competitors, Expansion opportunities, Advocacy & value realization, Product knowledge, Meeting scheduling), never a hardcoded org-specific topic. No
_cfields. Trend fields are flag-gated per org: probeabsolute_growth_percentage; if null, degrade to current-period volume + negative rate and say trends are unavailable. If the org is itself a vendor instance, ignore its internal/product-feedback topics and report only the canonical customer-facing parents.
Step 0: Topic + cohort + window
- Cohort (the differentiator): VoC is only as sharp as its scope. Default = whole active book, but the power is a specific cohort: a tier, a team (owner set), the at-risk accounts (
insight EXISTS ChurnRisk∨risk.risk_level >= 4), a renewal window, the churned set. Ask or infer which cohort; the topic profile changes completely by cohort. Pass it as thefilter.customerargument on every topic metric. - Topic: optional. Open VoC ("what are customers saying") → rank all canonical parents (Step 1) and surface the dominant + rising-negative themes. Topic VoC ("...about X") → go straight to the named parent and drill (Steps 2-3).
- Window: default
Past3Months(thedateRangeargument); the trend compares it to the prior period.
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 · 86 lines · 155 tokens per session scan A 60e09d1966c8
staircase-voice-of-customer is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 155 tokens to every session and 2,375 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…