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-no-qbr-ebr-schedulergit 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-no-qbr-ebr-scheduler)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/gainsight-no-qbr-ebr-scheduler"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/gainsight-no-qbr-ebr-scheduler/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-no-qbr-ebr-scheduler"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/gainsight-no-qbr-ebr-scheduler.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.00068 | $0.04067 |
| Opus 5 | $0.00034 | $0.02034 |
| Sonnet 5 | $0.00014 | $0.00813 |
| Haiku 4.5 | $0.00007 | $0.00407 |
Grade A, and why
gainsight-no-qbr-ebr-scheduler 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 12d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No QBR → EBR Scheduler
Discovery
Auto-trigger phrases:
- "which accounts need an EBR"
- "schedule my EBRs"
- "EBR pipeline"
- "who needs a QBR"
- "draft EBR invites"
- "accounts overdue for a business review"
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 (15-cap, OR not supported, determinism)../staircase-mcp-expert/references/analyst-data-models.md— structured queries per analysis type (Summary, Risk, Expansion — used per-account in Step 2 EBR-context fan-out)../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 (Email type) + Timeline recipes with HTML templates../gainsight-cs-mcp-expert/references/anti-patterns.md— gotchas, custom field requirements, HTML formatting
Output discipline (for any customer-facing write):
../../_shared/gainsight-output-best-practices.md
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
⚡ Pre-query quality gate (mandatory before any non-trivial Staircase query plan)
Canonical reference: plugins/gainsight-cs/skills/staircase-mcp-expert/references/query-patterns.md — top-of-doc Execution Checklist. 30-second scan before composing.
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.
- 12d ago First seen · 347 lines · 68 tokens per session scan A dea1f9b17acf
gainsight-no-qbr-ebr-scheduler is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 4,067 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…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.