post-purchase-upsell-flow

post-purchase-upsell-flow is a skill for Claude Code from autonnel/autonnel-skills. It costs 85 tokens per session (1,857 once invoked), scanned A, original, Apache-2.0.

A post-purchase offer flow that presents an upsell, cross-sell, bundle, or downsell after a customer has paid. An upsell offers a higher-value purchase, while a downsell offers a lower-priced alternative.

In plain words
What is it for?
Use it to design a one-click offer after checkout, monetize a thank-you page, choose between upsells and downsells, and connect the flow to existing payment and order handling.
Why use it?
It helps increase the average amount earned per order without adding another offer to the original checkout. The input notes that the main purchase is already complete when this flow begins.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the autonnel plugin — 6 skills shipped together

Good fit Use it to design a one-click offer after checkout, monetize a thank-you page, choose between upsells and downsells, and connect the flow to existing payment and order handling.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/autonnel/autonnel-skills/post-purchase-upsell-flow
Install

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.

Any agent
npx skills add autonnel/autonnel-skills --skill post-purchase-upsell-flow
Clone the repo
git clone --depth 1 https://github.com/autonnel/autonnel-skills

Made for: Claude Code.

Or install autonnel, the plugin that ships this one along with the rest of its 6 skills.

Wrote 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.

agentmods badge for post-purchase-upsell-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/autonnel/autonnel-skills/post-purchase-upsell-flow/github.svg)](https://agentmods.dev/skills/autonnel/autonnel-skills/post-purchase-upsell-flow)
Your own site
<a href="https://agentmods.dev/skills/autonnel/autonnel-skills/post-purchase-upsell-flow"><img src="https://agentmods.dev/badge/skills/autonnel/autonnel-skills/post-purchase-upsell-flow/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.

agentmods 80×15 button for post-purchase-upsell-flow

Your own site · 80×15
<a href="https://agentmods.dev/skills/autonnel/autonnel-skills/post-purchase-upsell-flow"><img src="https://agentmods.dev/badge/skills/autonnel/autonnel-skills/post-purchase-upsell-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,857 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 6 Aug 2026
  • Snyk warn 6 Aug 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.01857
Opus 5.5 $0.00034 $0.00743
Sonnet 5.5 $0.00017 $0.00371
Haiku 4.5 $0.00009 $0.00186

Measured 2mo ago against content hash 2249aa11ac76, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

post-purchase-upsell-flow 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 2mo 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.

post-purchase-upsell-flow/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Post-Purchase Upsell Flow

The step after payment is the cheapest revenue in a funnel: the customer has already converted, the payment method is already captured, and the offer costs nothing in ad spend. This skill covers designing that step and the technical requirements that make it actually work.

When to use

  • "How do I increase AOV" / "my ad costs are fine but revenue per order is too low"
  • Adding an upsell, cross-sell, bundle or downsell to an existing checkout
  • The thank-you page currently says only "thanks for your order"
  • Deciding between a pre-purchase bump and a post-purchase upsell

When not to use

  • Main funnel converts near zero - fix that first (landing-page-conversion-audit). An upsell on no traffic is arithmetic on zero.
  • High-ticket, sales-call-closed offers. The upsell there is a human conversation, not a page.

Pre-purchase vs post-purchase: pick deliberately

Pre-purchase (bump on the order form) Post-purchase (after payment)
Risk to main conversion Real - every added element on the order form can cost you the base sale None - the base order is already captured
Take rate Lower per offer, but seen by 100% of checkout visitors Higher per offer, seen only by buyers
Price ceiling Low (a small add-on) Higher (2-5x the base order is normal)
Payment friction None, same form Needs stored payment credentials to be one-click

Default recommendation: build the post-purchase upsell first. It cannot cannibalize the base conversion rate, so it is the only AOV lever that is risk-free to test. Add a pre-purchase bump later, and only behind an A/B test that watches base conversion rate as a guardrail metric.

Designing the offer

Rules that decide take rate

  1. Complementary, not bigger. "You bought the mat, here is the strap" beats "buy a second mat at 20% off". The customer's need is now solved; sell the thing that completes it.
  2. One decision per screen. A grid of four upsells converts worse than one offer with a clear yes/no.
  3. Yes must be one tap. Any re-entry of card details collapses take rate. This is a technical requirement, not a design preference - see below.
  4. No must be honest and easy. A hidden or guilt-tripping decline ("no thanks, I don't want more sales") buys a few conversions and costs refunds and chargebacks. Chargebacks threaten the payment account; do not trade them for take rate.
  5. Price relative to what they just paid. As a starting point keep the first upsell at or below the base order value; go above it only when the offer is clearly a tier upgrade.
  6. Time-bound only if true. "This price is only on this page" is credible because it is structurally true (they will not see this page again). Fake countdown timers are not, and buyers who feel tricked refund.

Read the full file on GitHub · 117 lines

Changes

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.

  1. 2mo ago First seen · 117 lines · 85 tokens per session scan A 2249aa11ac76

Subscribe to this mod's changes

post-purchase-upsell-flow is a skill published in the GitHub repository autonnel/autonnel-skills (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,857 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

shopify-admin

Write or explain Admin GraphQL queries and mutations for apps and integrations that extend the Shopify admin. Use when the user wants to understand, design, or generate the operation itself—even before deciding how to run it. Do not choose admin first for app monetization—charging merchants for the app itself via app…

Shopify/Shopify-AI-Toolkit · 226 tokens

shopify-onboarding-merchant

Set up a Shopify store. Use to make, build, or open a store (e.g. 'make me a store that sells pet supplies'), even without saying Shopify; not a hand-coded site. Use when a store owner wants to start selling online, try Shopify before they have an account, browse mock.shop reference stores, start from a mock…

Shopify/Shopify-AI-Toolkit · 220 tokens

shopify-shopifyql

Answer a merchant's analytics and reporting questions with ShopifyQL — Shopify's query language for aggregated store metrics that the Admin GraphQL API cannot compute. Choose this (not admin) whenever the ask is for numbers, totals, trends, or breakdowns rather than fetching or mutating individual records: including…

Shopify/Shopify-AI-Toolkit · 216 tokens

shopify-use-shopify-cli

Choose when the user needs Shopify CLI to run or fix something now: validate app or extension config on disk (shopify.app.toml, shopify.app. .toml, shopify.extension.toml); review or audit an app's code for security vulnerabilities; run or troubleshoot store workflows (shopify store auth, shopify store execute); or…

Shopify/Shopify-AI-Toolkit · 221 tokens

shopify-onboarding-dev

Get started building on Shopify. Use when a developer asks to build an app, build a theme, create a dev store, set up a partner account, scaffold a project, or get started developing for Shopify — including building an app in a specific backend language or framework (for example Laravel, Symfony, Django, Flask, Rails…

Shopify/Shopify-AI-Toolkit · 128 tokens

shopify-polaris-admin-extensions

Add custom actions and blocks from your app at contextually relevant spots throughout the Shopify Admin, including App Home UI extensions — the Shopify-hosted admin.app.home.render target (API version 2026-07 or later) that renders your app's landing page instead of an iframe. Covers the Intents API…

Shopify/Shopify-AI-Toolkit · 105 tokens