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 coleschaffer/copywritingskills-rmbc --skill bonus-stackgit clone --depth 1 https://github.com/coleschaffer/copywritingskills-rmbcWrote 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/coleschaffer/copywritingskills-rmbc/bonus-stack)<a href="https://agentmods.dev/skills/coleschaffer/copywritingskills-rmbc/bonus-stack"><img src="https://agentmods.dev/badge/skills/coleschaffer/copywritingskills-rmbc/bonus-stack.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.00041 | $0.02360 |
| Opus 5 | $0.00020 | $0.01180 |
| Sonnet 5 | $0.00008 | $0.00472 |
| Haiku 4.5 | $0.00004 | $0.00236 |
Grade A, and why
bonus-stack 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bonus-stack — 86% identical, 107 lines differ
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bonus-stack
Purpose
Design bonus stacks that increase perceived value without increasing fulfillment cost. Bonuses are the leverage in an offer — they add perceived value at a fraction of the actual cost, tipping the buyer's internal math from "maybe" to "yes." The best bonuses aren't random giveaways; they address a specific objection, complement the core product's mechanism, and feel expensive while costing almost nothing to deliver. This skill produces 3-5 bonuses with names, descriptions, perceived values, actual costs, and explicit rationale for why each one belongs in the stack.
Inputs
| Input | Required | Description |
|---|---|---|
core_product |
Yes | What the main product is, its mechanism, what transformation it delivers |
price_point |
Yes | Price of the core product — bonuses must feel proportional |
target_audience |
Yes | Who the buyer is — their objections, desires, and what they'd pay for separately |
fulfillment_constraint |
Yes | One of: digital_only (no physical shipping), physical_ok (can include physical items) |
Execution Protocol
Step 1 — Load Framework Context
Read rmbc-context/SKILL.md to load RMBC framework definitions. Bonus design is an RMBC exercise — Research reveals which objections bonuses must kill, the Mechanism determines which bonuses naturally extend the "why it works" story, the Brief sequences bonuses for maximum perceived value, and Copy names each bonus to feel like a standalone product.
Step 2 — Map the Objection Landscape
Before designing bonuses, identify the buyer's top 5 objections at the point of purchase. Every bonus must kill at least one:
| Objection Type | Example | Bonus Strategy |
|---|---|---|
| "Will it work for ME?" | Skepticism about personal results | Case study guide, assessment tool, personalization element |
| "I don't have time" | Implementation overwhelm | Quick-start guide, templates, checklists that reduce time to value |
| "What if I get stuck?" | Fear of confusion or complexity | FAQ resource, troubleshooting guide, community access |
| "Is it worth the money?" | Value skepticism | Bonus that would cost more than the product if purchased separately |
| "I can find this free" | Commodity perception | Unique/proprietary bonus that isn't available anywhere else |
| "I've tried X before and it failed" | Past failure baggage | Differentiation guide showing why this approach is different |
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.
- 6d ago First seen · 186 lines · 41 tokens per session scan A 4de92b60ca8b
bonus-stack is a skill published in the GitHub repository coleschaffer/copywritingskills-rmbc (30 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 2,360 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…