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 nthnclrk/enablement-skills --skill qbr-ebr-buildergit clone --depth 1 https://github.com/nthnclrk/enablement-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/nthnclrk/enablement-skills/qbr-ebr-builder)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/qbr-ebr-builder"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/qbr-ebr-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/nthnclrk/enablement-skills/qbr-ebr-builder"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/qbr-ebr-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.00080 | $0.00960 |
| Opus 5 | $0.00040 | $0.00480 |
| Sonnet 5 | $0.00016 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
qbr-ebr-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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QBR EBR builder
Write the review around customer outcomes. If it reads like a vendor activity recap, rewrite it.
A QBR or EBR is a customer-facing review unless the user asks for internal mode. If they want a standalone internal account diagnosis, use account-brief-builder. If they want a one-off executive meeting with an ask, use executive-briefing-builder.
Customer outcome. "Time-to-invoice dropped from 9 days to 4. You still miss the 2-day target you set in January. Decision: fund the AP automation work this quarter, or accept 4 days as the new baseline."
Vendor recap. "This quarter our team delivered 14 enablement sessions, launched two playbooks, and completed three QBRs. We remain committed to your success."
If the customer would hear internal risk language — churn risk, weak champion, discount ceiling — it is not a customer pack.
Confirm Inputs First
Ask only for the inputs that change the review:
- QBR or EBR, audience seniority, and the decisions you want in the room
- Customer goals and success criteria they already accepted
- Review period, baseline, and prior-cycle commitments
- Outcome metrics with source, as-of date, and whether the customer accepts the interpretation
- Format, and whether they also want an internal prep appendix
If evidence is thin, ask for the smallest blocking set. Do not invent metrics, logos, attribution, pricing, or customer commitments.
Read The Right Reference
Read references/qbr-ebr-structure.md for QBR vs EBR shape, the outcome test, and leakage rules. Skip it if the user already gave an agenda and only wants the narrative filled.
Default Workflow
- Name the mode. Customer-facing is the default. Internal prep is a separate appendix, only when asked. Done when you can point to which pages the customer will see.
- Name the decisions the room must make. One to three executive asks. If there is no decision, it is a status deck — rewrite until there is one.
- Reconcile the scorecard. Each metric: definition, source, as-of date, baseline, current value, evidence confidence. Attribution stays separate. Preserve conflicts. Correlation is not causation.
- Close the prior loop. Status of last cycle's commitments before any new work. Unconfirmed customer owners stay proposed.
- Write the outcome narrative. Goals, movement, interpretation, business impact. Cut vendor activity that does not change an outcome they care about.
- Surface only supported risks and opportunities. Trigger, impact, response. Customer-safe wording in the pack. Internal commercial risk stays in the appendix.
- Convert to a joint action plan.
Customer owner and internal owner on each item. Mark
draft,proposed,agreed, orchanged. Treat a customer date as a commitment only with confirmation evidence. - Leakage check. Internal risk language, negotiation posture, confidential commentary, unsupported attribution. If it would surprise the customer, it does not belong on their pages.
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.
- 10d ago First seen · 78 lines · 80 tokens per session scan A c6e621c5edd1
qbr-ebr-builder is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 20d ago), licensed MIT. It adds 80 tokens to every session and 960 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…