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 deciqAI/knowledge-skills --skill customer-relationship-laddergit clone --depth 1 https://github.com/deciqAI/knowledge-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/deciqai/knowledge-skills/customer-relationship-ladder)<a href="https://agentmods.dev/skills/deciqai/knowledge-skills/customer-relationship-ladder"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/customer-relationship-ladder/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/deciqai/knowledge-skills/customer-relationship-ladder"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/customer-relationship-ladder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00129 | $0.02023 |
| Opus 5 | $0.00064 | $0.01012 |
| Sonnet 5 | $0.00026 | $0.00405 |
| Haiku 4.5 | $0.00013 | $0.00202 |
Grade A, and why
customer-relationship-ladder 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Relationship Ladder
Overview
Most B2B teams treat relationship deepening as an attitude problem — be friendlier, schedule more QBRs. The Ladder reframes it as structural: each rung requires a fundamentally different operating model, and you cannot skip rungs.
| Rung | Name | Signal |
|---|---|---|
| 1 | Partial Fulfillment | Vendor meets stated need only; customer keeps alternatives warm |
| 2 | Basic Fulfillment | Vendor reliably delivers; customer stops shopping around |
| 3 | Deep Understanding | Vendor understands unstated needs; proactive insight delivery |
| 4 | Trusted Strategic Partner | Customer shares roadmap; joint planning occurs |
| 5 | Driver / Pioneer | Vendor shapes customer's strategy; co-creation; high switching cost |
Cross-skill composition: After jobs-to-be-done (surfaces jobs per rung). Before demand-leadership (Ladder = supply-side account; Demand Leadership = demand-side category). Alongside principal-agent to audit incentive alignment before Rung 4–5 joint planning.
When to Use
Trigger: Key account renewal at risk; team claims "strategic partner" but can't name one unstated need addressed this quarter; new CSM needs rapid diagnostic; deal lost on relationship despite best product; board asks "how do we become indispensable to top accounts?"
When NOT to use: Transactional/high-volume (<$500 ACV); customer prefers arms-length; fewer than 10 customers (use lean-startup first).
Coaching Novices (Adaptive Front Door)
Engine mode: concrete account → run The Process. Coach mode: unfamiliar → guide step by step. In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.
- "Tell me the last 3 things you did for this customer that were not in the contract." Blank = Rung 1–2.
- "Name one thing you did that they didn't ask for, but you knew they needed." Concrete answer = Rung 2→3 boundary.
- "Does the customer share internal strategic plans before they're finalized?" Yes = approaching Rung 4.
[WAIT — do not advance until user responds]
- "What would prevent you from being more proactive?" Answers: (a) don't know their business, (b) afraid to overstep, (c) they don't engage — each maps to a different rung-up move.
[WAIT — do not advance until user responds]
- Name one rung-up action with an owner and date — the single thing in 30 days evidencing one rung climbed.
[WAIT — do not advance until user responds]
What ships with it
2 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 · 122 lines · 129 tokens per session scan A 120f55452981
customer-relationship-ladder is a skill published in the GitHub repository deciqAI/knowledge-skills (10 stars, last pushed 9d ago), licensed MIT. It adds 129 tokens to every session and 2,023 once invoked, about $0.0006 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
edge-tts
Text-to-speech conversion using uvx edge-tts for generating audio from text. Use when (1) User requests audio/voice output with the "tts" trigger or keyword. (2) Content needs to be spoken rather than read (multitasking, accessibility, driving, cooking). (3) User wants a specific voice, speed, pitch, or format for TTS…
mcp-deepwiki
Skills for accessing and searching docs in DeepWiki/GitHub’s public code repositories can help users understand open-source project source codes, and users can also ask questions directly about the code docs.
tianqi
A weather-lookup workflow for Chinese locations, covering forecasts, hourly conditions, weather warnings, and daily-life indexes.
plan-payroll
Plans payroll cash: true loaded cost per hire (gross plus employer taxes, benefits, tools), a payroll calendar with cutoffs and cash-out dates, a scenario table for new hire vs raise vs contractor-vs-employee, and a payroll-to-revenue check against rough industry bands. Use when the user asks "can I afford to hire"…
cto-advisor
Records technical decisions that serve a business outcome: constraints, architecture options, build-or-buy tradeoffs, and a justified skill selection. Use when the CEO asks "which architecture fits", "should we build or buy", "which skill should this department use", or "review our technical plan".
maishou
A price-comparison workflow for products sold through major Chinese online marketplaces. It searches listings and can retrieve product details, purchase links, and available coupons.