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 modest-curator478/claude-skills --skill marketing-qbrgit clone --depth 1 https://github.com/modest-curator478/claude-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/modest-curator478/claude-skills/marketing-qbr)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/marketing-qbr"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/marketing-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/modest-curator478/claude-skills/marketing-qbr"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/marketing-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.00235 | $0.02927 |
| Opus 5 | $0.00118 | $0.01463 |
| Sonnet 5 | $0.00047 | $0.00585 |
| Haiku 4.5 | $0.00023 | $0.00293 |
Grade A, and why
marketing-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 12d 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.
This is a copy
100% identical to marketing-qbr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing QBR: The Quarterly Accountability Conversation That Builds or Erodes Credibility
This skill prepares a demand gen or RevOps Director to present quarterly marketing performance to executive leadership in a way that builds credibility, connects activity to business outcomes, and controls the narrative around results, including the quarters when results were below expectations.
The marketing QBR is not a reporting exercise. It is a credibility exercise. The CEO and CRO are not learning what happened from your QBR. They already know the pipeline number and the revenue number. What they are evaluating is whether you understand what drove those numbers, whether you can identify what is and is not working, and whether you have a clear-eyed plan for the next quarter. A Director who presents data confidently is worth less than a Director who demonstrates judgment about what the data means.
HOW TO SET UP THIS SKILL
Provide:
- Last quarter's key metrics: pipeline generated, pipeline contribution to revenue, CPL by channel, MQL to SQL conversion rate, any other metrics your leadership team follows
- Targets for the same metrics: what you committed to and what you delivered
- The programs that drove the most significant results, positive or negative
- Whether the quarter hit, missed, or exceeded expectations
- What leadership is currently most focused on: pipeline, revenue attribution, spend efficiency, or specific channels
- Any contested or sensitive items: attribution disputes, programs that underperformed, budget that was spent without clear return
The Structural Mistake Most Marketing QBRs Make
The default QBR structure is: here is what we did, here is what we measured, here is what it produced. This structure puts leadership in the position of drawing their own conclusions from your data. They will draw conclusions that reflect their priors, not your analysis. If the CRO already suspects that paid LinkedIn is a waste of budget, presenting LinkedIn metrics without context gives them evidence for the conclusion they already hold.
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.
- 12d ago First seen · 334 lines · 235 tokens per session scan A de22138c2716
marketing-qbr is a skill published in the GitHub repository modest-curator478/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 235 tokens to every session and 2,927 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to marketing-qbr, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
code-review
Pre-commit code review using code-reviewer agent for bug detection, security analysis, and quality assurance. Manual invocation only. Use before git commits to catch issues early. Blocks commits on REQUESTCHANGES verdict.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.