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 magnus919/agent-skills --skill conditional-customer-successgit clone --depth 1 https://github.com/magnus919/agent-skillsWrote 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/magnus919/agent-skills/conditional-customer-success)<a href="https://agentmods.dev/skills/magnus919/agent-skills/conditional-customer-success"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/conditional-customer-success/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/magnus919/agent-skills/conditional-customer-success"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/conditional-customer-success.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 209 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00100 | $0.03425 |
| Opus 5 | $0.00050 | $0.01713 |
| Sonnet 5 | $0.00020 | $0.00685 |
| Haiku 4.5 | $0.00010 | $0.00343 |
Grade A, and why
conditional-customer-success 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conditional Customer Success
A CONDITIONAL skill for products with recurring human relationships. This skill must never be loaded for every product context. It loads only when the product has accounts, renewals, QBRs, or a dedicated customer-success team. When those conditions are absent — for internal tools, pure transactional products, or public services without account-based engagement — this skill declines and routes the caller away.
When to Load (Should-Trigger Examples)
| Example | What makes it a match |
|---|---|
| B2B subscription product with named account managers | Accounts, renewals, dedicated CS team |
| Enterprise SaaS with quarterly business reviews | QBR cadence, account-tier engagement |
| Renewal-risk analysis needed for a contract portfolio | Renewal evidence, churn-risk signals |
| Product with an assigned customer-success team managing health plans | Success plans, health tracking |
| Account-expansion opportunity identified but adoption signals are mixed | Expansion with relationship context |
| Customer feedback loop — insight surfaced, product change made, customer communication needed | Closed-loop Voice of Customer |
When not to use
This skill must not be loaded for products without accounts, renewals, QBRs, or a customer-success team. See the should-not-trigger examples below.
When NOT to Load (Should-Not-Trigger Examples)
This skill must not load when the product context lacks the required preconditions. The skill must decline and route the caller away.
| Example | Why it does not apply |
|---|---|
| Internal developer tool with no accounts, no renewals, no QBRs | No recurring human relationship; no CS team |
| Pure transactional e-commerce product — one-time purchases, no account management | No accounts, no renewals, no QBRs, no CS team |
| Public-service benefit-application portal — no account-tier engagement, no CS team | No accounts (in the CS sense), no renewals, no QBRs |
| Consumer mobile game with subscription billing but no human CS relationship | Subscription alone is insufficient; no human CS relationship |
| Open-source project with community support but no paid accounts | No accounts, no renewals, no CS team |
| Internal analytics dashboard for a single team | No recurring relationship outside the team; no CS team |
What ships with it
8 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.
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 · 320 lines · 100 tokens per session scan A a8773aa69e89
conditional-customer-success is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 3,425 once invoked, about $0.0005 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…