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 mrpkk/vedic-muhurta-mcp --skill vedic-muhurtagit clone --depth 1 https://github.com/mrpkk/vedic-muhurta-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/mrpkk/vedic-muhurta-mcp/vedic-muhurta)<a href="https://agentmods.dev/skills/mrpkk/vedic-muhurta-mcp/vedic-muhurta"><img src="https://agentmods.dev/badge/skills/mrpkk/vedic-muhurta-mcp/vedic-muhurta/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/mrpkk/vedic-muhurta-mcp/vedic-muhurta"><img src="https://agentmods.dev/badge/skills/mrpkk/vedic-muhurta-mcp/vedic-muhurta.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.00086 | $0.00416 |
| Opus 5 | $0.00043 | $0.00208 |
| Sonnet 5 | $0.00017 | $0.00083 |
| Haiku 4.5 | $0.00009 | $0.00042 |
Grade A, and why
vedic-muhurta-planner 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 11d 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
Vedic Muhurta Planner
Find the best hour to act. Combines Swiss-Ephemeris-grade astronomy with transparent classical rules.
Workflow
- Clarify the event type — one of:
business_launch·travel·wedding·purchase·publication·healing·general - Fix the place — city from the built-in list or lat/lon; ask for timezone if not obvious.
- Scan via the
find_auspicious_windowstool (default 7 days, max 31). - Present top 3–5 windows as a table: local time · score · ruling planet · nakshatra · tithi.
- Always show reasons for each window and the Rahu Kala caveat.
Decision guide for scores
- 90+ — excellent window, safe to schedule
- 70–89 — good
- 50–69 — neutral, use only if nothing better in range
- <50 or flagged RAHU KALA — do not use
Fallback without tools
If no MCP tool is available, give only general guidance and say explicitly that precise muhurta requires calculation — never invent planetary hours.
Trigger phrases
"когда лучше запустить", "мухурта на сделку/свадьбу/поездку", "благоприятный день", "rahu kala today", "panchanga for tomorrow", "планетарные часы"
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.
- 11d ago First seen · 33 lines · 86 tokens per session scan A 6c88f7936125
vedic-muhurta-planner is a skill published in the GitHub repository mrpkk/vedic-muhurta-mcp (0 stars, last pushed 20d ago), licensed MIT. It adds 86 tokens to every session and 416 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…