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 w95/awesome-claude-corporate-skills --skill qbr-buildergit clone --depth 1 https://github.com/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/qbr-builder)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/qbr-builder"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/qbr-builder/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/w95/awesome-claude-corporate-skills/qbr-builder"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/qbr-builder.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.00025 | $0.03469 |
| Opus 5 | $0.00013 | $0.01734 |
| Sonnet 5 | $0.00005 | $0.00694 |
| Haiku 4.5 | $0.00003 | $0.00347 |
Grade A, and why
qbr-builder 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 9d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QBR Builder
Overview
Master Quarterly Business Reviews (QBRs) that showcase mutual value, identify expansion opportunities, mitigate churn risk, and align customer success with business objectives. Effective QBRs build strategic partnerships and unlock growth.
QBR Structure & Agenda
1. Pre-QBR Preparation (2 weeks before)
Gather Data:
- Usage analytics (logins, features, sessions)
- Health indicators (support tickets, satisfaction scores, NPS)
- Financial data (spend, utilization, ROI)
- Roadmap alignment (upcoming features, releases)
- Risk assessment (contract renewal date, alternatives risk, budget constraints)
Stakeholder Coordination:
- Schedule 60-90 minute meeting
- Invite: Account Executive, CSM, Product Manager, Technical Lead
- From customer: VP/Director, Key users, Finance (if expanding)
- Confirm agenda 1 week prior
Prepare Customized Materials:
- Account health summary (one-page overview)
- Usage analytics dashboard (key metrics visualization)
- ROI calculation (value delivered vs. investment)
- Customer testimonial/case study (if available)
- Executive summary (2-page deck)
2. Account Health Score
Build Health Scorecard (1-100 scale):
Health Category | Weight | Score | Calculation
-----------------|--------|-------|---------------------
Product Usage | 25% | 85 | Login frequency 4x/week; 8 of 10 features used
Engagement | 20% | 90 | Training attendance 100%; active in support
Support/NPS | 20% | 80 | NPS 50; 2 support tickets/month (norm)
Expansion Signals | 20% | 75 | Uses in 2 departments; growth interest unclear
Renewal Risk | 15% | 95 | Contract expires in 9 months; no churn signals
OVERALL HEALTH | 100% | 84 | HEALTHY (green zone: 70-100)
Health Zone:
- GREEN (80-100): Strong account; growth opportunity
- YELLOW (60-79): Adequate but monitor; may need intervention
- RED (<60): At-risk; immediate action needed
Usage Metrics Dashboard:
Metric | Target | Actual | Trend | Analysis
--------|--------|--------|-------|----------
Monthly Active Users | 50 | 42 | Down 5% | 1 power user on leave
Logins Per User/Mo | 15 | 12 | Flat | Normal usage pattern
Features Utilized | 8/10 | 8 | Up 1 | Using advanced reporting
Session Length (min) | 30 | 28 | Down | Still productive
Customer Health Score | 80+ | 84 | Up 4 | Trending positive
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.
- 9d ago First seen · 427 lines · 25 tokens per session scan A a53bd42716ef
qbr-builder is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 3,469 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.