design-relationship-tiering-system

design-relationship-tiering-system is a skill for Claude Code from jeffreytse/grimoire-core. It costs 87 tokens per session (2,189 once invoked), scanned A, original, MIT.

A guide for grouping professional contacts into relationship tiers and setting how often to contact each group.

In plain words
What is it for?
Use it to organise a professional network, choose contact frequencies, and schedule regular follow-ups.
Why use it?
It reduces the risk of neglecting valuable relationships simply because they are not currently top of mind.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it to organise a professional network, choose contact frequencies, and schedule regular follow-ups.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-relationship-tiering-system
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill design-relationship-tiering-system
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 skills.

Wrote 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.

agentmods badge for design-relationship-tiering-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-relationship-tiering-system/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-relationship-tiering-system)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-relationship-tiering-system"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-relationship-tiering-system/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.

agentmods 80×15 button for design-relationship-tiering-system

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-relationship-tiering-system"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-relationship-tiering-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.02189
Opus 5 $0.00044 $0.01094
Sonnet 5 $0.00017 $0.00438
Haiku 4.5 $0.00009 $0.00219

Measured 7d ago against content hash ae8f08baa32f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

design-relationship-tiering-system 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 7d 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.

skills/business/leadership/skills/design-relationship-tiering-system/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Relationship Tiering System

Assign each contact in your professional network an explicit tier based on their value and depth of relationship, set a minimum contact frequency for each tier, and actively schedule touchpoints against that cadence — because an unmanaged network defaults to contacting only whoever is currently top-of-mind, silently losing valuable but infrequently-encountered relationships to simple neglect.

Why This Is Best Practice

Why best: Human relationship-maintenance capacity is finite and does not scale with the number of people you meet — without an explicit system, contact frequency defaults to recency and convenience (whoever you happen to run into or think of), not to a contact's actual value or the relationship's fragility. A contact who is high-value but low-frequency-by-default (someone you only naturally encounter once every few years) is exactly the relationship an unmanaged network loses first, because nothing in an ad hoc system prompts a touchpoint before the relationship has already gone cold. Explicit tiering with a minimum cadence per tier converts relationship maintenance from a passive, memory-dependent process into an active, scheduled one — matching maintenance effort to actual relationship value rather than to accidental recency.

Robin Dunbar (1992) and subsequent research: Dunbar's foundational research, and the substantial body of subsequent work it generated, established that humans maintain cognitively meaningful relationships in a limited, layered structure — a small inner circle of very close relationships, surrounded by successively larger but shallower layers of less-frequently-maintained relationships, with total capacity for meaningfully maintained relationships bounded regardless of how many people are nominally "in the network." This provides the underlying constraint that makes explicit tiering necessary: since maintenance capacity for close, effortful contact is genuinely limited, an explicit system for allocating that limited capacity across a growing network is required once the network exceeds what memory alone can track.

Read the full file on GitHub · 69 lines

Changes

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.

  1. 7d ago First seen · 69 lines · 87 tokens per session scan A ae8f08baa32f

Subscribe to this mod's changes

design-relationship-tiering-system is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 22d ago), licensed MIT. It adds 87 tokens to every session and 2,189 once invoked, about $0.0004 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.