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 SkillMedev/skills --skill customer-success-qbrgit clone --depth 1 https://github.com/SkillMedev/skillsWrote 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/skillmedev/skills/customer-success-qbr)<a href="https://agentmods.dev/skills/skillmedev/skills/customer-success-qbr"><img src="https://agentmods.dev/badge/skills/skillmedev/skills/customer-success-qbr/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/skillmedev/skills/customer-success-qbr"><img src="https://agentmods.dev/badge/skills/skillmedev/skills/customer-success-qbr.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.00135 | $0.01929 |
| Opus 5.5 | $0.00054 | $0.00772 |
| Sonnet 5.5 | $0.00027 | $0.00386 |
| Haiku 4.5 | $0.00014 | $0.00193 |
Grade A, and why
customer-success-qbr 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 11d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Success QBR
A QBR is not a product demo or a support recap. It is a business conversation that proves the value you delivered, aligns on the customer's goals, and opens the door to expansion and renewal. Run badly - usage stats to a champion-only room - it trains the customer that QBRs are skippable, and the renewal conversation starts cold at day 90. Run well, it is the single best retention tool you have.
Operating procedure
Follow the steps in order: the room decides whether the meeting matters, the pre-work decides whether you have anything to say, and the value section must land before any expansion ask is credible.
Step 1: Gather inputs
Collect these before building anything. Where a number is unverified, label it a guess and confirm it with the champion before the meeting.
- The customer's stated goals from last quarter, in their exact words (from the prior QBR notes or kickoff doc). If none exist, the first agenda item becomes setting them.
- Contract facts: ARR, renewal date, products owned, seats licensed vs. active.
- Usage data mapped to business outcomes: hours saved, revenue influenced, cost avoided, risk reduced - validated with the champion, not asserted.
- Health inputs: adoption depth and breadth, executive engagement in the last quarter, support ticket volume and sentiment, escalation history.
- Attendee list with titles. Identify the economic buyer and executive sponsor explicitly.
Step 2: Get the right room or escalate
A QBR with only your champion is a status call. Require the economic buyer or executive sponsor - the people who renew and expand. If they decline twice in a row, treat the absence itself as a churn signal: log it in the health score (executive engagement goes red) and escalate internally. Do not run the full QBR format for a champion-only room; downgrade it to a working session and rebook the executive review.
Step 3: Score account health before the meeting
Build the score from leading indicators, not lagging ones. Weight four components:
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.
- 11d ago Changed · +2 lines d968381d082f
- 1mo ago First seen · 111 lines · 135 tokens per session scan A 1f9212720651
customer-success-qbr is a skill published in the GitHub repository SkillMedev/skills (19 stars, last pushed 3d ago), licensed MIT. It adds 135 tokens to every session and 1,929 once invoked, about $0.0005 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-03.
Other skills, from other repositories
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
ai-assisted-performance-review
Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or…
role-redesign-for-ai
Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or when planning…