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 upsell-sequence-writergit 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/upsell-sequence-writer)<a href="https://agentmods.dev/skills/coleschaffer/copywritingskills-rmbc/upsell-sequence-writer"><img src="https://agentmods.dev/badge/skills/coleschaffer/copywritingskills-rmbc/upsell-sequence-writer/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/coleschaffer/copywritingskills-rmbc/upsell-sequence-writer"><img src="https://agentmods.dev/badge/skills/coleschaffer/copywritingskills-rmbc/upsell-sequence-writer.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.00038 | $0.01522 |
| Opus 5 | $0.00019 | $0.00761 |
| Sonnet 5 | $0.00008 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
upsell-sequence-writer 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 11d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
upsell-sequence-writer
Purpose
Generate a post-purchase email sequence (3-5 emails) that ascends customers from their initial purchase to a higher-ticket complementary offer. These emails deploy after the buyer has already said yes — trust is established, the product is in hand (or arriving), and the window for ascension is open. Each email must deliver genuine value before bridging to the upsell. The sequence arc moves from gratitude through value delivery to the offer, with urgency closing the window. Every email uses RMBC principles compressed into short-form format.
Inputs
| Input | Required | Description |
|---|---|---|
initial_product |
Yes | What the customer already purchased — name, price, core promise |
upsell_product |
Yes | The higher-ticket offer — name, price, what it does, how it complements the initial purchase |
upsell_price |
Yes | Price of the upsell with any discount framing |
target_audience |
Yes | Who the buyer is — demographics, pain points, desires, sophistication level |
sequence_length |
No | Number of emails: 3, 4, or 5 (default: 5) |
key_mechanism |
No | The upsell product's unique mechanism (output from /mechanism-ideation) |
send_timing |
No | Days between emails (default: Day 1, 3, 5, 7, 9) |
Execution Protocol
Step 1 — Load Framework Context
Read rmbc-context/SKILL.md to load RMBC framework definitions. Upsell sequences deploy RMBC across multiple touchpoints — Research informs the value content, Mechanism justifies the upsell, Brief structures the sequence arc, Copy executes each email.
Step 2 — Define the Sequence Arc
Map the emotional journey across the sequence:
| Role | Emotional State | RMBC Focus | |
|---|---|---|---|
| 1 — Thank You | Validate purchase, deliver quick win | Excited, hopeful | Research (reinforce their decision) |
| 2 — Value Delivery | Teach something useful related to their purchase | Engaged, learning | Research → Mechanism tease |
| 3 — Bridge | Connect initial product's limitation to upsell need | Curious, aware of gap | Mechanism reveal |
| 4 — Offer | Present the upsell with full value stack | Desire, trust | Brief → Copy (full pitch) |
| 5 — Urgency Close | Final window, scarcity, guarantee restatement | Fear of missing out | Copy (close) |
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.
- 11d ago First seen · 132 lines · 38 tokens per session scan A f6fb6dd11206
upsell-sequence-writer is a skill published in the GitHub repository coleschaffer/copywritingskills-rmbc (30 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,522 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…
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…