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 openephemeris/openephemeris-MCP --skill chinese-vedic-astrologygit clone --depth 1 https://github.com/openephemeris/openephemeris-MCPWrote 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/openephemeris/openephemeris-mcp/chinese-vedic-astrology)<a href="https://agentmods.dev/skills/openephemeris/openephemeris-mcp/chinese-vedic-astrology"><img src="https://agentmods.dev/badge/skills/openephemeris/openephemeris-mcp/chinese-vedic-astrology/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/openephemeris/openephemeris-mcp/chinese-vedic-astrology"><img src="https://agentmods.dev/badge/skills/openephemeris/openephemeris-mcp/chinese-vedic-astrology.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.00077 | $0.03318 |
| Opus 5 | $0.00039 | $0.01659 |
| Sonnet 5 | $0.00015 | $0.00664 |
| Haiku 4.5 | $0.00008 | $0.00332 |
Grade A, and why
chinese-vedic-astrology 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chinese & Vedic Astrology
Two distinct Eastern systems. Don't conflate them — Chinese astrology is based on the lunisolar calendar and Five Elements; Vedic is sidereal and tied to the Nakshatra (lunar mansion) system.
When to Use Which
| Question | System |
|---|---|
| "What's my Chinese zodiac animal?" | Chinese (basic) |
| "What's my BaZi / Four Pillars / Eight Characters?" | Chinese BaZi |
| "Element balance / lucky element?" | Chinese BaZi |
| "What's my Vedic chart / Jyotish?" | Vedic |
| "What's my nakshatra / lunar mansion?" | Vedic |
| "What dasha am I in?" | Vedic |
| "Tropical vs sidereal — what's the difference for me?" | Vedic |
Required Information
For both:
- Full birth date
- Birth time (for BaZi, hour pillar requires this; for Vedic, all houses + nakshatra are time-sensitive)
- Birth location
Standard Procedure for Birth-Data Endpoints
Any endpoint that takes a birth chart (natal, synastry, composite, transits, returns, progressions, Human Design, Vedic, ACG) MUST follow this sequence. Skipping any step produces a wrong chart — usually wrong by hours of arc.
Step 1 — Resolve location to coordinates
If you don't already have precise lat/lon, call:
GET /location/autocomplete?query=<city, country>&limit=5
Confirm the right hit with the user if there's ambiguity (e.g. "Portland, OR" vs "Portland, ME"). Record the latitude and longitude of the chosen result.
Step 2 — Resolve timezone for that location AT THE BIRTH DATE
Historical timezone rules matter. A city's UTC offset in 1962 may differ from today (DST rules, war time, jurisdiction changes). Always look up the timezone for the specific birth date.
POST /timezone/lookup
{ "latitude": <lat>, "longitude": <lon> }
Response gives an IANA timezone string like "America/Los_Angeles". The BirthLocation field below REQUIRES this — it is not optional.
Step 3 — Build the request body
The SubjectRequest schema requires birth_datetime, birth_location, and name. The IANA timezone goes into birth_location.timezone:
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 · 286 lines · 77 tokens per session scan A a4e467a675ef
chinese-vedic-astrology is a skill published in the GitHub repository openephemeris/openephemeris-MCP (4 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 3,318 once invoked, about $0.0004 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
astrologer-api
Build astrology features using the Astrologer API — natal charts, synastry, transits, composite charts, solar/lunar returns, moon phases, compatibility scores, and AI-optimized context. Use when the user asks to add astrology to an app, generate birth charts, calculate compatibility, render SVG charts, get planetary…
panchanga-api
Vedic astrology (Jyotish) REST API powered by Swiss Ephemeris. 19 endpoints: Panchanga, Kundali (300+ Yogas, Ashtakavarga, Doshas), KP system (249 sub-lords), Dasha, Muhurta, Choghadiya, Compatibility, Transits, Vrata calendar, Remedies, Panchanga Search, and more. All calculations use Lahiri ayanamsha and sidereal…
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.