Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gs-bbluhm/gainsight-mcp-plugins/plugin install staircaseWrote 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-1on1-prep)<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-1on1-prep"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-1on1-prep/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-1on1-prep"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-1on1-prep.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.00108 | $0.02451 |
| Opus 5.5 | $0.00043 | $0.00980 |
| Sonnet 5.5 | $0.00022 | $0.00490 |
| Haiku 4.5 | $0.00011 | $0.00245 |
Grade A, and why
staircase-1on1-prep 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staircase 1:1 Prep (manager / one teammate)
A manager walks into a 1:1 wanting one thing: "here's this person's book, here's how they're actually doing, here's what to raise." This skill answers that for exactly one teammate, curated for the manager's perspective (is this person overwhelmed, does their book need help, what do I bring up), not the IC's own working view. It reuses ../staircase-book-triage/'s validated 7-motion account table (by reference, scoped to one person's book) rather than re-deriving it, and adds the personal-effort/overwhelmed layer that skill doesn't carry.
This is the single-teammate lens, from a manager's chair. For the whole team at once use ../staircase-team-manager/; for that person's own working view of their book (the IC's Monday cockpit) use ../staircase-book-triage/ with scope set to them; for one account's full deep read use ../staircase-account-deep-dive/ or ../staircase-risk-check/; to zoom out to portfolio risk use ../staircase-risk-radar/.
Foundation references (read BEFORE composing any query)
../staircase-mcp-expert/SKILL.mdstep 0: the resolved book-owner field; do not assumeOwner.../staircase-mcp-expert/references/report-recipes.md:book.context,team.rollup, andlifecycle.evidence;advanced-report-patterns.mdfor the argument system and lifecycle events (§1, §3).../staircase-book-triage/SKILL.md: the 7-motion lens table (churn / unspoken-renewal-risk / silent-risk / blindsided / fragile-save / cadence-break / expansion-in-motion) and the deterministic churn-lifecycle-event detection. This skill applies the SAME table, scoped to one person's book, not a rewrite of it.../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.
Scope (decide first)
- Use the resolved book-owner field. Read
scope.book_owner_fieldfrom~/.staircase-mcp/user-profile.md; if absent, run the foundation's first-call contract (scope.membership). - Resolve the person. If arriving via
staircase-team-manager'ssendPrompthand-off, the team baseline (overwhelmed_threshold_hrs, this person's percentile) is already in the prompt text; use it directly, don't re-pull the whole team. If invoked standalone, resolve the name with a directrun_reportlookup onuser.full_name Equal "<name>"(generate_reportis a fallback).
What ships with it
2 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.
- 25d ago First seen · 101 lines · 108 tokens per session scan A b44bf53d6aec
staircase-1on1-prep is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 108 tokens to every session and 2,451 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…