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 bjorn-ingmanson/thefroject-plugins --skill qbr-buildergit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/qbr-builder)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/qbr-builder"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/qbr-builder.svg" alt="Measured on agentmods" 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.00035 | $0.01066 |
| Opus 5 | $0.00017 | $0.00533 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00107 |
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 8d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QBR Builder
A QBR is not a product demo or a support recap. It is a strategic conversation about the customer's business outcomes and how your partnership drives them.
Input Required
- Customer goals — what they wanted to achieve this quarter (check previous QBR in
outputs/) - Usage data — adoption metrics, feature usage, active users
- Support data — ticket volume, resolution times, satisfaction scores
- Value metrics — measurable outcomes tied to their goals
- Account context — org changes, budget shifts, competitive activity
- Relationship data — stakeholder map, engagement level, NPS responses
QBR Structure
Section 1 — Partnership Summary (2 min)
One slide. Set the frame for the conversation:
| Element | Content |
|---|---|
| Relationship tenure | [X months/years] |
| Current investment | [$ARR] |
| Products/modules | [What they use] |
| Key stakeholders | [Names and roles in the meeting] |
| This quarter's focus | [Agreed goals from last QBR] |
Section 2 — Goals and Outcomes (10 min)
For each goal set last quarter:
| Goal | Target | Actual | Status | Evidence |
|---|---|---|---|---|
| [Goal 1] | [Metric] | [Metric] | ✅/⚠️/❌ | [Data source] |
| [Goal 2] |
For each goal, prepare a brief narrative:
- What was the goal?
- What did we do together to pursue it?
- What was the measurable result?
- What did we learn?
Section 3 — Usage and Adoption (5 min)
| Metric | Last Quarter | This Quarter | Change | Benchmark |
|---|---|---|---|---|
| Active users | [vs. similar customers] | |||
| Feature adoption | ||||
| Key action frequency | ||||
| Time in product |
Highlight:
- Features they should be using but are not
- Adoption trends (growing, flat, declining)
- Power users who could champion expansion
Section 4 — Support and Health (3 min)
| Metric | Value | Trend | Context |
|---|---|---|---|
| Tickets opened | |||
| Avg resolution time | |||
| CSAT score | |||
| Open issues | [List any P1/P2] |
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.
- 8d ago First seen · 138 lines · 35 tokens per session scan A 99b8f6269f83
qbr-builder is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,066 once invoked, about $0.0002 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-31.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
diagnostic-stem-delivery
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.
chengfeng-check-updates
An environment manager for a video-editing system. It checks whether its skills and runtime—the software needed to run them—are installed and compatible.