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 agentmods add skills/mxm-sys/opencode-tianji/liurennpx skills add Mxm-sys/opencode-tianji --skill liurengit clone --depth 1 https://github.com/Mxm-sys/opencode-tianjiWhat 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 | $0.00069 | $0.00407 |
| Opus 5 | $0.00034 | $0.00204 |
| Sonnet 5 | $0.00014 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
liuren 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 yesterday.
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
小六壬占课(轻量流程)
第 0 步:须知
一事一占,心中默念所问之事。用一两句话告知即可。
第 1 步:收集必要信息(question 工具)
- 所问之事(必问):想测什么?(求财/出行/婚姻/失物/健康/合作等)
- 起课依据:当前时间(月日时),或用户报数(数字覆盖月/日,小时取当前时辰)。
第 2 步:调用工具
- 用当前时间:调用
liuren(不传或传 datetime)。 - 报数:调用
liuren,传入 month/day 覆盖。
第 3 步:输出规范
- 【落宫】最终落宫(大安/留连/速喜/赤口/小吉/空亡)、五行、吉凶。
- 【断辞】断辞白话翻译,紧扣所问之事落具体建议。
- 【总结】纯白话说明结果与建议。
- 注明"仅供参考,现实决策请结合实际情况"。
参考资料
- 占课工具:opencode-tianji 插件提供 liuren 工具(六宫断辞据包内 data/liuren.json)
- 六宫掌诀:包内 data/liuren.json(宫名/位/五行/吉凶/断辞/白话/总结)
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.
- yesterday First seen · 33 lines · 69 tokens per session scan A ebeacad7c979
liuren is a skill published in the GitHub repository Mxm-sys/opencode-tianji (0 stars, last pushed 24d ago), licensed MIT. It adds 69 tokens to every session and 407 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…