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.
git clone --depth 1 https://github.com/adarshj322/rishi-ai-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/commands/adarshj322/rishi-ai-mcp/compatibility)<a href="https://agentmods.dev/commands/adarshj322/rishi-ai-mcp/compatibility"><img src="https://agentmods.dev/badge/commands/adarshj322/rishi-ai-mcp/compatibility/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/commands/adarshj322/rishi-ai-mcp/compatibility"><img src="https://agentmods.dev/badge/commands/adarshj322/rishi-ai-mcp/compatibility.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.00008 | $0.00489 |
| Opus 5 | $0.00004 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
compatibility 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 10d 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
Compatibility Analysis Workflow
When the user wants to analyze relationship compatibility between two partners, execute these steps:
Steps
-
Gather Both Birth Details:
- Male: DOB, Time, Lat, Lon
- Female: DOB, Time, Lat, Lon
- Confirm Person 1 = Male, Person 2 = Female (traditional Ashtakoot)
-
Fetch Compatibility Data: Call
calculate_compatibilitywith both sets of birth parameters. -
Read 8 Ashtakoot Kutas (36 points total):
- Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi
- Each kuta has specific weights; sum gives total compatibility score
-
Extra Kutas: Read additional factors:
- Mahendra: Nakshatra durability — same group nakshatras strengthen bond
- Rajju: Nakshatra element mismatch — affects longevity
- Stree Deergha: Female specific — affects offspring hope
- Vedha: Nakshatra blocking — can impede relationship
- Bad Constellations: Specific nakshatras that clash
-
Exception Logic: Check if any Nadi/Rajju exceptions apply that mitigate afflictions.
-
Kuja Dosha Analysis:
- Mars in houses 2, 4, 7, 8, 12 for both partners
- Scoring based on dignity and house placement
- Mild/Moderate/Severe verdict
-
Synthesize & Deliver:
- Overall Score: X/36 with grade (Excellent/Good/Fair/Poor)
- Strength Areas: Which kutas are favorable
- Challenge Areas: Which kutas need remedy work
- Kuja Dosha Status: If present, severity and remedies
- Exception Benefits: If exceptions apply, how they help
- Timing: When favorable periods activate based on dasha
- Remedies: Sattvic remedies for weak kutas
Tools
calculate_compatibility: 36-point Ashtakoot + Kuja Dosha + extra kutas
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.
- 10d ago First seen · 47 lines · 8 tokens per session scan A 3154e94eab03
compatibility is a command published in the GitHub repository adarshj322/rishi-ai-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 489 once invoked, about $0.0000 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 commands, from other repositories
mylife-setup
A guided interview for filling a MYLIFE vault with information about your personality, surroundings, money, work, and relationships. Astrology and birth-chart details are optional.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.