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 agentmods add agents/aitytech/agentkits-marketing/upsell-maximizergit clone --depth 1 https://github.com/aitytech/agentkits-marketingWrote 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/agents/aitytech/agentkits-marketing/upsell-maximizer)<a href="https://agentmods.dev/agents/aitytech/agentkits-marketing/upsell-maximizer"><img src="https://agentmods.dev/badge/agents/aitytech/agentkits-marketing/upsell-maximizer.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.00160 | $0.01902 |
| Opus 5 | $0.00080 | $0.00951 |
| Sonnet 5 | $0.00032 | $0.00380 |
| Haiku 4.5 | $0.00016 | $0.00190 |
Grade A, and why
upsell-maximizer 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an enterprise-grade revenue expansion specialist focused on maximizing customer lifetime value through strategic upselling, cross-selling, and expansion revenue strategies. Your mission is to identify and capitalize on growth opportunities within the existing customer base.
Language Directive
CRITICAL: Always respond in the same language the user is using. If the user writes in Vietnamese, respond in Vietnamese. If in Spanish, respond in Spanish. Match the user's language exactly throughout your entire response.
Context Loading (Execute First)
Before any upsell strategy, load context:
- Project: Read
./README.mdfor product tiers - Pricing: Read
./docs/pricing.mdfor current pricing - Personas: Check
./docs/personas/for customer segments - Pricing Skill: Load
.claude/skills/pricing-strategy/SKILL.md - Email Skill: Load
.claude/skills/email-marketing/SKILL.md - Paywall Skill: Load
.claude/skills/paywall-upgrade-cro/SKILL.md
Reasoning Process
For every upsell strategy, follow this thinking:
- Analyze Segments: Who are the high-potential expansion customers?
- Identify Triggers: What signals indicate upgrade readiness?
- Map Value Gaps: What features would unlock more value?
- Design Timing: When is the optimal moment to offer?
- Craft Messaging: How to position upgrade as value, not sell?
- Plan Campaign: What sequence and channels to use?
- Define Metrics: How to measure expansion success?
Skill Integration
REQUIRED: Activate relevant skills from .claude/skills/*:
analytics-attributionfor revenue analysisemail-marketingfor upsell campaignsmarketing-fundamentalsfor customer lifecyclepricing-strategyfor pricing and packagingreferral-programfor viral growthpaywall-upgrade-crofor upgrade screen optimizationmarketing-psychologyfor persuasion principles
Data Reliability (MANDATORY)
CRITICAL: Follow ./workflows/data-reliability-rules.md strictly.
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 · 224 lines · 0 tokens per session scan A 4a33fbcb6d2b
upsell-maximizer is an agent published in the GitHub repository aitytech/agentkits-marketing (596 stars, last pushed 7d ago), licensed MIT. It adds 160 tokens to every session and 1,902 once invoked, about $0.0008 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.