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-handoffgit 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-handoff)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-account-handoff"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-account-handoff/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-handoff"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-account-handoff.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.00106 | $0.02027 |
| Opus 5.5 | $0.00042 | $0.00811 |
| Sonnet 5.5 | $0.00021 | $0.00405 |
| Haiku 4.5 | $0.00011 | $0.00203 |
Grade A, and why
staircase-account-handoff 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staircase Account Handoff
For the moment someone inherits an account by promotion, reorg, leave coverage, or normal rotation. This turns Staircase's communication history into a concrete first-90-days brief, so the new owner walks in with a real point of view instead of a cold company record. Output is a markdown brief, not a CRM write.
Foundation references
Read these before composing the query if you have not in this session:
../staircase-mcp-expert/: query mechanics and the Handoff Analysis data model (the richest, most structured analyst output).../../_shared/staircase-output-best-practices.md: the house style.
When to use
Trigger phrases:
- "I'm taking over [account]" / "I just inherited [account]"
- "build me an onboarding brief for [account]"
- "handoff brief for [account]" / "new owner brief for [account]"
- "I'm the new owner on [account]"
Optimized for: Cowork (card + tabs) and Code (markdown + optional file). The brief is the deliverable the new owner uses on day one.
Step 1: Resolve the account
Call staircase_account_lookup(name=<account>) first.
- High-confidence single match: proceed.
- Multiple low-confidence matches: STOP and ask which account. Do not guess.
- No match: tell the user; without communication data there is nothing to synthesize. Offer to run the skill once communications start flowing.
Step 1.5: Pull the structured scaffold (cheap, deterministic)
Call staircase_account_info(account_id) once first. 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, owner/CSM names, and (most relevant here) the stored Handoff fields (Handoff strategic summary, Handoff primary objectives) plus the AI Summary, Churn Risk, and Renewal summaries. When the Handoff analyst has fired, these give the new owner a factual spine before any narrative. (Note: on active accounts that were never formally handed off, the handoff fields may be empty (verified live); fall back to the Handoff Analysis query in Step 2.)
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 · 161 lines · 106 tokens per session scan A 32ba5f0735f5
staircase-account-handoff is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 106 tokens to every session and 2,027 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…