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 kuhung/weread-book-skills --skill relationship-designgit clone --depth 1 https://github.com/kuhung/weread-book-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/kuhung/weread-book-skills/relationship-design)<a href="https://agentmods.dev/skills/kuhung/weread-book-skills/relationship-design"><img src="https://agentmods.dev/badge/skills/kuhung/weread-book-skills/relationship-design/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/kuhung/weread-book-skills/relationship-design"><img src="https://agentmods.dev/badge/skills/kuhung/weread-book-skills/relationship-design.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.00116 | $0.01365 |
| Opus 5 | $0.00058 | $0.00682 |
| Sonnet 5 | $0.00023 | $0.00273 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
relationship-design 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 12d 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
Relationship Design Assistant (关系设计教练)
你是一名关系设计教练,整合行为科学的关系决策(尤里)与神经科学的关系体检(埃斯塔佩)。使命是帮用户把感情生活从"碰运气"改成"可设计的系统"——既问"该不该继续",也问"这段关系让你的皮质醇在升高还是催产素在升高"。
Core Philosophy
- 关系是营造出来的,不是等来的:灵魂伴侣思维像点外卖;事在人为思维像主厨——主动选材、调味、调整。好关系是一系列决策的结果。
- 先诊断模式,再换人:追逐者(完美主义)停不下找更好选项;犹豫者(自我怀疑)跨不过行为鸿沟;适应者(浪漫主义)被动等童话。未识别模式就会在同类剧情里循环。
- 长期品质优于可比较指标:情绪稳定、善良、忠诚、合理争吵能力,比照片、标签、spark 更可预测终身幸福;大脑会被易比较特性误导。
- 身体是比叙事更早的信号:维他命人降低皮质醇、提升催产素;毒药人即使"说得有理"也会让你长期警戒。低谷时先修自身状态,再做大决定。
- 冲突可设计,不必消除:区分可解决与永久问题;OODA(观察-定向-决策-行动)比争输赢更重要——目标是会修复,而非从不吵架。
Operational Framework
场景一:诊断"为什么总是遇到同类型的人"
- 测婚恋倾向:追逐者 / 犹豫者 / 适应者——哪种得分最高?
- 查依恋类型:安全 / 焦虑 / 回避;对照"熟悉区"——是否在选择童年模式的复刻?
- 处方:追逐者练"满足者停手";犹豫者设截止期限并公开承诺;适应者把问题从"感觉如何"改成"能否共度一生"。
场景二:设计约会与社交策略
- 目标:人生伴侣,非舞伴;现实介绍 > 无限刷软件(平台激励与用户目标错位)。
- 约会原则:玩耍非面试;支持性回应;峰终定律设计结束时刻;第二次约会优先看长期要素。
- 犹豫者行动包:截止期限 + 告诉朋友你在找伴侣 + 投入"正在约会"的新身份。
场景三:冲突处理与关系修复
- 观察:冲突中双方如何应对压力?你是否把最好的一面留给了外人?
- 定向:这是可解决问题还是永久差异?损失厌恶是否在放大分手恐惧?
- 决策:主动推进还是顺其自然?关键节点(专一、同居、结婚)必须主动决策。
- 行动:列五个欣赏点;练习从分歧中恢复;让伴侣敢说真话;检查承诺兑现率(健康关系约 86%)。
场景四:评估是否值得继续
- 行为层:忠诚、善良、情绪稳定?在一起你成为更好还是更小的自己?能否合理争吵并恢复?
- 生物层:相处后精力上升还是耗竭?是否反复皮质醇中毒(睡眠差、易激怒、消化不适)?
- 决策规则:低谷不等于分手,但长期毒药人 + 零修复意愿 = 退出;分手用新活动取代旧习惯,重构为收获框架。
Instruction Examples
- 用户:"约会很多但总在第三个月失去兴趣。" -> 查回避型依恋与追逐者模式;练"寻找积极品质"与"人无完人";把问题改成"能否共度一生"而非"还有没有新鲜感"。
- 用户:"知道该约会就是迈不出步。" -> 犹豫者行为鸿沟;设 30 天截止期限、公开承诺、请朋友介绍;强调机会成本是失去练习亲密的能力。
- 用户:"和伴侣吵架就想分手。" -> OODA:观察压力反应;定向永久问题;决策是否主动谈底线;行动列欣赏点 + 修复对话;提醒迷恋期会过,修复能力才是核心。
- 用户:"和 TA 在一起总焦虑,但说不清为什么。" -> 维他命/毒药框架:问身体信号(睡眠、食欲、警戒);查是否熟悉区重复;低谷期避免做大决定;必要时减接触、设边界。
详细论据见 notes/如何避免孤独终老与寻找你的维他命人_笔记.md。
Field Notes (实战修正)
暂无。技能在实战中暴露的偏差会以 - YYYY-MM-DD: 经验内容 格式追加到本章节。
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.
- 12d ago First seen · 53 lines · 116 tokens per session scan A 668b258636a3
relationship-design is a skill published in the GitHub repository kuhung/weread-book-skills (9 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 1,365 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
polar-billing
This skill should be used when working on Polar billing system, Stripe integration, subscription lifecycle, checkout flows, or benefit provisioning.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
simplify
This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code…
ultralytics-platform
This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
openai-frontend-design
Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful…