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 gainsight-meeting-processorgit 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/gainsight-meeting-processor)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/gainsight-meeting-processor"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/gainsight-meeting-processor/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/gainsight-meeting-processor"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/gainsight-meeting-processor.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.00062 | $0.07046 |
| Opus 5 | $0.00031 | $0.03523 |
| Sonnet 5 | $0.00012 | $0.01409 |
| Haiku 4.5 | $0.00006 | $0.00705 |
Grade A, and why
gainsight-meeting-processor 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 10d 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 — 563 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gainsight Meeting Processor
Discovery
Auto-trigger phrases:
- "I just had a call with [customer]"
- "process my [customer] call"
- "post-call for [customer]"
- "[customer] sync recap"
- "[customer] meeting recap"
- "recap my [customer] call"
Why this matters: Headline workflow that exercises both Staircase AI and Gainsight CS MCPs together. The Staircase fan-out differentiates this from transcript-only post-call tools. Risk and sentiment claims are grounded in 60-90 days of communication data, not just the call.
Optimized for: Cowork (interactive cards + approval gates) and Code (markdown + structured prompts). Cowork is the primary optimization target.
Foundation references
Read these BEFORE composing operations:
User profile (if exists):
~/.gainsight-mcp/user-profile.md— name, role, filter field, filter value. Apply role-appropriate defaults + filter automatically. If profile doesn't exist, prompt user to rungainsight-mcp-setup.
Foundation skills (for MCP mechanics):
../staircase-mcp-expert/references/query-patterns.md— Staircase query patterns../staircase-mcp-expert/references/anti-patterns.md— Staircase gotchas../staircase-mcp-expert/references/analyst-data-models.md— structured queries per analysis type (Handoff, Expansion, Risk, Churn, Renewal, Summary)../gainsight-cs-mcp-expert/references/tool-inventory.md— Gainsight CS tool reference../gainsight-cs-mcp-expert/references/org-discovery.md— Tier/Segment + team-member field discovery (org-bespoke)../gainsight-cs-mcp-expert/references/write-path-patterns.md— canonical CTA + Task + Timeline + SP recipes with HTML templates../gainsight-cs-mcp-expert/references/anti-patterns.md— G3.1-G3.11 gotchas, custom field requirements, HTML formatting
Output discipline (for any customer-facing write):
../../_shared/gainsight-output-best-practices.md(v1.1)
Rendering discipline (for Cowork app-feel):
../mcp-app-design/references/patterns.md— tab structure, action tee-up sequence, preference question cards, working mode picker, color/badge semantics
What ships with it
7 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.
- 10d ago First seen · 563 lines · 62 tokens per session scan A bdb40003464a
gainsight-meeting-processor is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 7,046 once invoked, about $0.0003 per session on Opus 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.