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 quivly/skills --skill qbr-prepgit clone --depth 1 https://github.com/quivly/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/quivly/skills/qbr-prep)<a href="https://agentmods.dev/skills/quivly/skills/qbr-prep"><img src="https://agentmods.dev/badge/skills/quivly/skills/qbr-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/quivly/skills/qbr-prep"><img src="https://agentmods.dev/badge/skills/quivly/skills/qbr-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.00054 | $0.00741 |
| Opus 5.5 | $0.00022 | $0.00296 |
| Sonnet 5.5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
qbr-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 2mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QBR Prep
You build the content for a business review that earns its meeting slot: value proven with their numbers, honest gaps, and a forward plan worth an executive's time.
Core principle: usage is evidence; outcomes are the story — a QBR that reads as a usage report wastes an executive hour.
Workflow
- Establish the baseline: what success criteria were set at kickoff or the last QBR (
search-calls, review prior QBR notes). The QBR's spine is "you said X mattered — here's where X stands". - Build the value story (
get-usage,trend-analysis): quarter-over-quarter usage narrative, adoption milestones hit, workflows now running through the product. Convert usage into outcome language wherever possible (time saved, revenue influenced, risk reduced). - Be honest about gaps: under-adopted capabilities they're paying for, stalled initiatives, unresolved asks from last quarter. Bring each with a proposed fix.
- Check commercial posture (
get-contracts,get-revenue,get-health-score): renewal distance, growth precedent, health — this calibrates how forward the renewal/expansion conversation should be. - Draft the forward plan: next quarter's priorities in their language, our asks of them (stakeholder time, data access, rollout support), and any expansion motion that genuinely serves their goals.
Output Format
QBR: {Customer} — {quarter}
Executive summary slide — 3 bullets: value headline, health headline, next-quarter headline
Value delivered — success criteria vs. actuals, with numbers and trend charts to pull
Honest gaps — each with a proposed fix and owner
Next quarter plan — priorities, milestones, mutual commitments
Renewal/expansion positioning — how forward to be, and the specific motion if any
Meeting design notes — who must attend, 2-3 discovery questions to ask live, topics to pre-wire before the room
Guidelines
- A QBR that reads as a usage report wastes an exec meeting; usage is evidence, outcomes are the story.
- Bring last QBR's commitments and score ourselves publicly — credibility compounds.
- If value evidence is thin, the QBR's honest job is realignment, not celebration — say so in the prep.
- Pre-wire anything surprising; the QBR room is for alignment, not ambushes.
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.
- 2mo ago First seen · 56 lines · 54 tokens per session scan A 75b1bda9909a
qbr-prep is a skill published in the GitHub repository quivly/skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 741 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
nitrostack-tools-resources-prompts
Guidelines and patterns for defining Tools, Resources, and Prompts in a NitroStack application with schema validation via Zod, including caching, rate-limiting, and base64 file uploads.
prisma-postgres-setup
Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to "set up a database", "create a Prisma Postgres project", "get a connection string", "connect my app to Prisma Postgres", or "provision a database".
nitrostack-ui-widgets
Best practices for linking tools to interactive frontend widgets using @Widget and @nitrostack/widgets SDK (including state sync, tool calling, display modes, media queries, and chat actions).
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".
nitrostack-mcp-app-architecture
Best practices and guidelines for bootstrapping, defining modules, using dependency injection, managing server lifecycles, and handling events in the NitroStack SDK.
nitrostack-middleware-pipeline
Best practices for implementing and applying Guards, Interceptors, Middleware, Pipes, and Exception Filters in the NitroStack SDK.