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/muhurtha)<a href="https://agentmods.dev/commands/adarshj322/rishi-ai-mcp/muhurtha"><img src="https://agentmods.dev/badge/commands/adarshj322/rishi-ai-mcp/muhurtha/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/muhurtha"><img src="https://agentmods.dev/badge/commands/adarshj322/rishi-ai-mcp/muhurtha.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.00011 | $0.00513 |
| Opus 5.5 | $0.00004 | $0.00205 |
| Sonnet 5.5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
muhurtha 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 2mo 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
Muhurtha (Electional Astrology) Workflow
When the user wants to find the best time for an important activity (marriage, travel, business, education, house entry, medical), execute these steps:
Steps
-
Confirm Activity Type: Must be one of:
marriage— wedding Muhurthatravel— journey Muhurthabusiness— new venture, signingeducation— starting studies, examshouse_entry— grihapraveshamedical— surgery, treatment
-
Gather Parameters: Date range, Time (if specific), Location (Lat, Lon, Timezone).
-
Fetch Muhurtha Data: Call
check_muhurtha_toolwith activity type and parameters. -
Read Verdict:
auspicious: Full green light — all factors favorablemixed_favorable: Mostly good with minor considerationsmixed: Caution needed — weigh pros and consinauspicious: Avoid or reschedule if possible
-
Score Analysis: Read
score(positive×10 - negative×15). Higher = better. -
Positive/Negative Factors: Parse specific reasons for verdict.
-
Panchang Suddhi: Check tithi, vara, nakshatra, yoga, karana purity.
-
Marriage-specific: If
marriageactivity, also read:- Sagraha — planetary alliance check
- Shashtashta — 60th part of both luminaries
- Bhrigupta Shatka — Bride's Mars placement analysis
- Kujaasthama — Mars position severity
-
Synthesize & Deliver:
- Verdict: Clear recommendation
- Best Time: Specific date/time if score is favorable
- Positive Factors: What's working in your favor
- Negative Factors: What to be aware of
- Remedies: Any pujan, charities, or mantras to strengthen the Muhurtha
- Alternative: If current date is poor, suggest better date range
Tools
check_muhurtha_tool: Electional astrology for 6 activity types
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.
- 2mo ago First seen · 51 lines · 11 tokens per session scan A 0ecfd40f307c
muhurtha is a command published in the GitHub repository adarshj322/rishi-ai-mcp (2 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 513 once invoked, about $0.0000 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.
muhurtha compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| muhurthaadarshj322/rishi-ai-mcp | Command | 2 | 5d ago | MIT | A | 11 | Claude Code |
| mylife-setupyys5584/mylife-vault | Command | 3 | 1mo ago | none | A | 32 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |