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 dhicoc/wuyun-liuqi-skills --skill yunqi-clinicalgit clone --depth 1 https://github.com/dhicoc/wuyun-liuqi-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/dhicoc/wuyun-liuqi-skills/yunqi-clinical)<a href="https://agentmods.dev/skills/dhicoc/wuyun-liuqi-skills/yunqi-clinical"><img src="https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/yunqi-clinical/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/dhicoc/wuyun-liuqi-skills/yunqi-clinical"><img src="https://agentmods.dev/badge/skills/dhicoc/wuyun-liuqi-skills/yunqi-clinical.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.00125 | $0.01902 |
| Opus 5 | $0.00063 | $0.00951 |
| Sonnet 5 | $0.00025 | $0.00380 |
| Haiku 4.5 | $0.00013 | $0.00190 |
Grade A, and why
yunqi-clinical 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
五运六气临床应用子技能
适用范围
- 根据运气病机分析结果确定治则治法
- 五运太过不及的参考方药选择
- 六气司天在泉的参考针灸选穴
- 运气养生调理建议（起居、饮食、情志）
- 运气治法与传统辨证论治的结合应用
前置依赖
MUST：本子技能无独立脚本依赖（文档化推理），但 MUST 先完成以下两步：
- 调用
yunqi-calc获取推算结果（大运、司天在泉、客主加临）- 调用
yunqi-pathogenesis完成病机分析（五运病机、六气病机、太过不及、运气合病）未获取推算结果和病机分析前，不得进入临床应用环节。
推荐工作流
Step 1/4：获取推算与病机结果
ACT: 确认已调用 yunqi-calc 和 yunqi-pathogenesis
- 确认以下信息已获取：
- 大运属性及太过/不及判断（来自 yunqi-calc）
- 司天在泉及客主加临（来自 yunqi-calc）
- 五运病机定位（来自 yunqi-pathogenesis）
- 六气病机定位（来自 yunqi-pathogenesis）
- 运气合病判断（来自 yunqi-pathogenesis）
- 确认病机分析报告完整后，方可进入治则治法环节
Step 2/4：确定治则治法
ACT: 查阅 references/zhize_zhifa.md
- 根据太过不及确定治则：
- 太过之年：抑其太过，扶其不胜
- 不及之年：扶其不足，抑其所不胜
- 根据司天在泉确定治则：
- 司天之气胜 → 治所胜之腑
- 在泉之气胜 → 治所胜之腑
- 根据客主加临确定治则：
- 客主不相得 → 调和客主，以平为期
- 查五运太过不及治法表及六气司天治法表
- 引用运气治法名言（出自素问七篇）作为理论依据
Step 3/4：选择方药/针灸
ACT: 查阅 references/fangyao_xuanze.md 或 references/zhenjiu_xuanxue.md
方药选择（查 fangyao_xuanze.md）：
- 根据五运太过不及选择参考方药
- 根据六气司天选择参考方药
- 遵循选用原则：非固定方，而是根据运气格局提供参考方向
- MUST NOT 给具体剂量，须由执业医师定夺
针灸选穴（查 zhenjiu_xuanxue.md）：
- 根据五运太过不及选择参考选穴
- 根据六气司天选择参考选穴
- 选穴原则：补本经原穴（扶正），泻克我经原穴（祛邪）
- MUST 标注：需由执业针灸师操作
Step 4/4：给出养生建议
ACT: 查阅 references/yangsheng_tiaoli.md
- 根据五运年份确定养生重点（按木火土金水分）
- 根据六气司天确定养生重点（按六气分）
- 按六步主气调整起居饮食（节气养生）
- 太过之年：抑其太过（养生方向）
- 不及之年：扶其不足（养生方向）
- 养生建议可以更具体（非临床诊断，无需免责声明的限制较方药宽松）
常见误区
| 问题 | 原因 | 解决方案 |
|---|---|---|
| 不加免责声明直接给方药 | 临床建议须附加免责 | MUST 附加医学免责声明 |
| 给具体剂量 | 须由执业医师决定 | MUST NOT 给具体剂量 |
| 脱离辨证论治 | 运气只是参考维度之一 | 结合患者实际辨证 |
| 跳过病机分析直接给方药 | 未完成 yunqi-pathogenesis | 先完成病机分析再进临床 |
| 方药与治法不一致 | 未查 zhize_zhifa.md | 先定治则再选方药 |
| 针灸选穴未标注执业要求 | 忽略安全提示 | MUST 标注需执业针灸师操作 |
输出要求
- 临床应用建议须包含以下要素：
- 运气治则治法（太过/不及治则、司天在泉治则）
- 参考方药（按五运/六气分类，不给具体剂量）
- 参考针灸选穴（按五运/六气分类，标注执业要求）
- 养生调理建议（起居、饮食、情志）
- 方药部分 MUST 附加医学免责声明
- 针灸部分 MUST 标注需由执业针灸师操作
- 输出须标明引用的参考文档名称
- 养生建议可以更具体，不受临床诊断免责限制
路由上下文
- 上游入口：
modules/yunqi-pathogenesis/（提供病机分析结果：脏腑定位、太过不及、运气合病判断） - 下游出口：医案沉淀 →
case-journal/（记录运气临床应用医案） - 同级关联：文献支撑 →
modules/yunqi-classics/（提供经典原文引用与理论依据）
What ships with it
4 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.
- 12d ago First seen · 136 lines · 125 tokens per session scan A 5fb49c2cb323
yunqi-clinical is a skill published in the GitHub repository dhicoc/wuyun-liuqi-skills (42 stars, last pushed 27d ago), licensed MIT. It adds 125 tokens to every session and 1,902 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…