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.
git clone --depth 1 https://github.com/wuji-labs/hetu-luoshuWrote 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/commands/wuji-labs/hetu-luoshu/hetu-luoshu)<a href="https://agentmods.dev/commands/wuji-labs/hetu-luoshu/hetu-luoshu"><img src="https://agentmods.dev/badge/commands/wuji-labs/hetu-luoshu/hetu-luoshu/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/commands/wuji-labs/hetu-luoshu/hetu-luoshu"><img src="https://agentmods.dev/badge/commands/wuji-labs/hetu-luoshu/hetu-luoshu.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.00039 | $0.00691 |
| Opus 5 | $0.00019 | $0.00345 |
| Sonnet 5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
hetu-luoshu 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.
What it actually says
/hetu-luoshu
手动触发 HeTu LuoShu skill。把一个 judgment / 系统 / 决策（$ARGUMENTS）丢进河图洛书四步推演机，得到一份「叩兩端·观其变·求其中」的辩证全景，而非单值结论。
若 $ARGUMENTS 为空，先问用户「要推演的对象是什么」。
触发后执行（standing procedure）
- 读取
SKILL.md四底层原则；典源细节按需下钻reference/yijing.md。 - 执行四步推演法：
- 叩两端（阴阳为体）— 列对象的阳面（显/刚/升/外/动）与阴面（隐/柔/降/内/静），把两极各问到底，标最大张力处。
- 立卦象（卦象为用）— 映射八卦基本态（健/悦/丽/动/入/陷/止/顺），指出主导态、缺位态、相荡态。需细节查集团
shared/daotong/data/gua-knowledge.json（只读，取结构语义不取占断）。 - 观变易（变易为机）— 给现态/趋势/临界后反态，标临界点（穷·极）与反转条件（变·通），找"动之微"。
- 求时中（执两用中）— 在当下时位给最恰当的"度"，说明此度随哪些条件移动，把决定权交还使用者。
- 全程不做吉凶占断、不预测具体未来、不为医疗/投资/法律决策背书。
输出格式（固定状态行 + 四段）
[河图洛书 | 对象：<X> | 主导卦：<卦德> | 缺位：<卦德> | 趋势：<↑/↓/临界> | 时中：<一句>]
▎叩两端 阳：… ｜ 阴：… ｜ 最大张力：…
▎立卦象 主导：… 缺位：… 相荡：…
▎观变易 现态：… 趋势：… 临界点：… 反转条件：… 动之微：…
▎求时中 当下最恰当的度：… 随…条件移动。决定权在你。
末尾附一行免责：本推演为思维框架，非占卜/预测，非专业决策依据。
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 · 34 lines · 39 tokens per session scan A 746b6c286e25
hetu-luoshu is a command published in the GitHub repository wuji-labs/hetu-luoshu (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 691 once invoked, about $0.0002 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.