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 m3taz-ahmed/ai-globals --skill client-retentiongit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/client-retention)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/client-retention"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/client-retention/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/m3taz-ahmed/ai-globals/client-retention"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/client-retention.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.00027 | $0.00541 |
| Opus 5 | $0.00014 | $0.00270 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
client-retention 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.
What it actually says
[SKILL] client-retention [OBJ] Maximize client lifetime value — proactive check-ins, timely upsells/cross-sells, and a referral engine that turns happy clients into new business.
[RULES]
- [REQ] Lifecycle map: post-delivery → 30-day check-in → quarterly review → renewal/upsell → referral ask. Each step scheduled in
lead-generation-crm. - [REQ] Health score: track satisfaction (NPS/CSAT), on-time delivery, repeat engagement. Flag at-risk (<60) for human outreach.
- [CMD] Context7 IDs:
twentyhq/twenty(opportunity/renewal),lago/getlago(subscription/retainer),chatwoot/chatwoot(relationship inbox). - [REQ] Upsell triggers: new need detected, scope growth, anniversary. Offer via
pricing-strategy(retainer/package). Never surprise-price mid-contract. - [REQ] Cross-sell: map complementary services (e.g., SEO client →
content-marketing); one relevant offer per review. - [REQ] Referral program: ask at peak satisfaction; give template + incentive (link
affiliate-manager). Track sources in CRM. - [REQ] Free-first: Twenty (AGPL) for accounts, Lago for retainers, Chatwoot (MIT) for touch; paid CS tools only as parity.
- [REQ] Arabic/RTL: Arabic clients get RTL check-in templates, relationship etiquette per
arabic-freelance, local holiday awareness. - [REQ] Win-back: lapsed clients get a 2-touch reactivation with a relevant offer; respect suppression (see
marketing-compliance). - [REQ] Measurement: retention %, expansion MRR, referral rate, NPS. Feed
marketing-analytics.
[PROHIBIT]
- No upsell before value is demonstrated.
- No excessive/unscheduled check-in spam.
- No referral request from dissatisfied clients.
- No Arabic retention message without RTL + etiquette.
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 · 39 lines · 27 tokens per session scan A a04e0f9e7438
client-retention is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 541 once invoked, about $0.0001 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-31.
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…