compatibility-synastry

compatibility-synastry is a skill for Claude Code, Codex from openephemeris/openephemeris-MCP. It costs 53 tokens per session (2,584 once invoked), scanned A, original, MIT.

A guide for comparing two people’s birth charts using astrology methods called synastry, composite, and Davison or midpoint charts. These methods describe how the charts interact and how the relationship is represented as a whole.

In plain words
What is it for?
Use it for romantic, friendship, or business-partnership compatibility questions involving two complete birth charts.
Why use it?
It organizes the birth details and chart-building steps needed for a compatibility reading, including checking locations and birth-time accuracy.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for romantic, friendship, or business-partnership compatibility questions involving two complete birth charts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openephemeris/openephemeris-mcp/compatibility-synastry
Install

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.

Any agent
npx skills add openephemeris/openephemeris-MCP --skill compatibility-synastry
Clone the repo
git clone --depth 1 https://github.com/openephemeris/openephemeris-MCP

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for compatibility-synastry

README.md
[![agentmods](https://agentmods.dev/badge/skills/openephemeris/openephemeris-mcp/compatibility-synastry/github.svg)](https://agentmods.dev/skills/openephemeris/openephemeris-mcp/compatibility-synastry)
Your own site
<a href="https://agentmods.dev/skills/openephemeris/openephemeris-mcp/compatibility-synastry"><img src="https://agentmods.dev/badge/skills/openephemeris/openephemeris-mcp/compatibility-synastry/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.

agentmods 80×15 button for compatibility-synastry

Your own site · 80×15
<a href="https://agentmods.dev/skills/openephemeris/openephemeris-mcp/compatibility-synastry"><img src="https://agentmods.dev/badge/skills/openephemeris/openephemeris-mcp/compatibility-synastry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,584 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.02584
Opus 5.5 $0.00021 $0.01034
Sonnet 5.5 $0.00011 $0.00517
Haiku 4.5 $0.00005 $0.00258

Measured 1mo ago against content hash e8c624f6ddfb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

compatibility-synastry 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 1mo 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.

skills/compatibility-synastry/SKILL.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Compatibility & Synastry

Use this skill whenever someone asks how two people work together — romantically, in friendship, or in partnership. Three complementary tools:

Tool Question it answers
Synastry "How do our energies interact?" (each person's planets aspecting the other's)
Composite "What is the relationship itself like?" (a third chart for the bond)
Davison / Midpoint "What's the time-space midpoint of our two charts?" (an alternative composite based on real averaged ephemeris time + location)

Required Information

Two complete subjects — for EACH person:

  1. Full birth date
  2. Birth time (precision matters; flag if missing)
  3. 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:

{
  "subject": {
    "name": "Subject",
    "birth_datetime": { "iso": "1990-04-15T14:30:00" },
    "birth_location": {
      "latitude": 41.8781,
      "longitude": -87.6298,
      "timezone": "America/Chicago",
      "city": "Chicago",
      "country": "United States"
    }
  }
}

Read the full file on GitHub · 236 lines

Changes

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.

  1. 1mo ago First seen · 236 lines · 53 tokens per session scan A e8c624f6ddfb

Subscribe to this mod's changes

compatibility-synastry is a skill published in the GitHub repository openephemeris/openephemeris-MCP (5 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,584 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

astrologer-api

Integrate the hosted Astrologer API through RapidAPI for SVG charts, astrology data, Moon phases, planetary hours and XML context. Use when writing or debugging clients for this service.

g-battaglia/Astrologer-API · 42 tokens

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…

degen0root/panchanga_api · 96 tokens

api-integration-architect

Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.

sickn33/agentic-awesome-skills · 33 tokens

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).

trpc/trpc · 75 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens