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/bazinpx skills add Mxm-sys/opencode-tianji --skill bazigit 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.00070 | $0.00449 |
| Opus 5 | $0.00035 | $0.00225 |
| Sonnet 5 | $0.00014 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
bazi 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 2d 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
八字四柱排盘(轻量流程)
第 0 步:须知
需相对精确的出生时间(年月日+时辰);时辰不准会影响排盘,向用户说明。
第 1 步:收集必要信息(question 工具)
- 出生时间(必问):公历或农历年月日时,越精确越好;只到日则时柱按午时缺省。
- 性别(必问):男/女,决定大运顺逆。
- 出生地(可选):省/市,用于换算经度定时辰;不提供按东八区(经度 120)。
第 2 步:调用工具
调用 bazi,传入:datetime、性别、经度(可选)。
第 3 步:输出规范
- 【四柱】年月日时四柱干支,点明日主(代表命主自己)。
- 【命盘】十神/地支藏干/纳音/五行统计与大运,每条术语(十神/纳音/日主/大运)紧跟白话翻译。
- 【总结】纯白话说明五行强弱、最需注意的方面与建议。
- 注明"仅供参考,现实决策请结合实际情况"。
参考资料
- 排盘工具:opencode-tianji 插件提供 bazi 工具(十神/藏干/纳音/大运据包内 data/bazi.json、data/ganzhi.json)
- 干支算法:包内 lib/ganzhi.ts(真太阳时/干支推算)
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.
- 2d ago First seen · 33 lines · 70 tokens per session scan A 656b5d3eb307
bazi is a skill published in the GitHub repository Mxm-sys/opencode-tianji (0 stars, last pushed 25d ago), licensed MIT. It adds 70 tokens to every session and 449 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…