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 liqiongyu/lenny_skills_plus --skill retention-engagementgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/retention-engagement)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/retention-engagement"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/retention-engagement/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/liqiongyu/lenny_skills_plus/retention-engagement"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/retention-engagement.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.00032 | $0.02414 |
| Opus 5 | $0.00016 | $0.01207 |
| Sonnet 5 | $0.00006 | $0.00483 |
| Haiku 4.5 | $0.00003 | $0.00241 |
Grade A, and why
retention-engagement 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 9d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retention & Engagement
Scope
Covers
- Diagnosing retention + engagement (cohorts/curves, frequency, segments, drop-offs)
- Identifying the activation / “aha moment” and reducing time-to-value
- Designing habit + re-engagement interventions (daily return, reminders, content loops)
- Creating accruing value and ethical switching costs (“mounting loss”)
- Turning insights into a prioritized experiment + measurement plan
When to use
- “Improve retention / reduce churn”
- “Increase engagement / DAU/WAU”
- “Define our activation / aha moment”
- “D1/D7 retention is low—fix onboarding and time-to-value”
- “Create a retention experiment backlog and a 30/60/90 plan”
When NOT to use
- You don’t have (or can’t assume) a stable value proposition / ICP (use
problem-definition). - You’re primarily deciding pricing/packaging/paywalls (this skill can add retention context but won’t replace pricing work).
- You need acquisition loop design (use
designing-growth-loops). - You need to synthesize qualitative churn feedback before proposing experiments (use
analyzing-user-feedbackor interviews). - The problem is specifically first-time onboarding UX (signup flow, empty states, guided setup) rather than full-lifecycle retention (use
user-onboarding). - You want to apply behavioral science frameworks (habit loops, nudge theory, loss aversion mechanics) as the primary lens rather than a retention metrics lens (use
behavioral-product-design). - You need to determine whether you have product-market fit before optimizing retention (use
measuring-product-market-fit).
Inputs
Minimum required
- Product + target user/ICP and 1–2 key segments
- Current stage (pre-PMF / early PMF / growth / mature)
- Best-available baseline metrics (even rough):
- retention (D1/D7/D30 or weekly cohort), churn, engagement (DAU/WAU/MAU), activation rate, time-to-value
- Onboarding flow summary (steps/screens + where users drop)
- Constraints: timebox, engineering/design capacity, allowed channels (email/push/in-app), privacy/legal/brand limits
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval/eval_config.json 1.8 KB
- eval/SHOWCASE.md 5.9 KB
- eval/with_skill.md 40 KB
- eval/without_skill.md 22 KB
- README.md 1.7 KB
- references/CHECKLISTS.md 2.5 KB
- references/EXAMPLES.md 2.1 KB
- references/INTAKE.md 2.1 KB
- references/RUBRIC.md 4.3 KB
- references/SOURCE_SUMMARY.md 2.4 KB
- references/TEMPLATES.md 3.3 KB
- references/WORKFLOW.md 5.0 KB
- skillpack.json 372 B
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.
- 9d ago First seen · 153 lines · 32 tokens per session scan A ba00631f1ccc
retention-engagement is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,414 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-09-03.
Other skills, from other repositories
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.