git:20260829.46f8ea3 to git:20260901.38c3ad3

---

name: horosa-agent

description: >-

chart, solar return, progressions, primary directions, horary, electional 择日, birth-time

rectification, 八字 bazi, 紫微斗数 ziwei, 大六壬, 奇门遁甲 qimen, 太乙, 金口诀, 六爻, 梅花心易,

河洛理数, 铁板神数, 塔罗 tarot, 天文地占 geomancy, 老黄历, AstroCartoGraphy, celebrity birth data,

Chinese esoteric history. Trigger on 起盘 排盘 起课 起卦 算命 推运 看盘 合盘 卜卦 择日 生时校正,

fortune-telling, divination, chart casting, or any Horosa/星阙 reading. Never hand-calculate.

license: AGPL-3.0-only

dependencies:

tools:

- type: mcp

name: horosa

note: >-

Local Horosa Skill MCP server (Python 3.12 + uv + offline runtime). Register with

`uv run --directory <repo>/horosa-skill horosa-skill client config --format codex`

(see examples/clients/codex.md for the full Codex setup, timeouts, and env whitelist).

---

# Horosa Agent Skill (Codex / agentskills.io entry)

Thin client-agnostic contract. The **single policy source** is

[`skills/horosa-agent/SKILL.md`](../../../horosa-skill/skills/horosa-agent/SKILL.md) — read it

(and its `references/`) before deep work. Maintainer/repo law: `AGENTS.md`.

## Non-negotiable rules

1. **Never hand-calculate** any Horosa/星阙 technique (no shell/Python/JS/web formulas, no memorized

tables). Every 盘/课/卦/运 comes from a `horosa` MCP tool call (`horosa_astro_chart`,

`horosa_cn_qimen`, `horosa_cn_liureng_gods`, …) or the `horosa-skill` CLI.

2. **Clarify before calling**: if a result-changing setting is missing (birth/event time, place,

timezone, gender, house system, 起局方式, 贵人体系, target year), ask the user a short question

with options first. Tools reject unconfirmed calls with `agent_guidance.required`; after the user

answers, retry with `agent_confirmed_settings: true` (or `defaults_accepted: true` when they

accept defaults) plus `clarification_notes`. Never self-confirm; never switch tools to bypass the

gate. In non-interactive runs (`codex exec`), surface the question as your final answer instead

of guessing.

3. **Read results only from `export_snapshot.export_text` / `.sections`** — that text is the chart.

Do not restate numbers that are not in it, and do not invent sections it lacks.

4. If `horosa` tools are absent from the tool list: first turn after a cold start may simply be too

early (Codex waits ~1s for optional servers; the runtime warms in ~45s) — retry next turn. Still

absent → the server is not configured; point the user at `examples/clients/codex.md`.

5. Errors carry structured recovery: on `details.agent_recovery`, relay `prompt_to_user` verbatim

and stop. On transport errors, suggest `horosa-skill doctor` / `horosa-skill selfcheck`.