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 fatenava/fatenava-mcp --skill destiny-chartgit clone --depth 1 https://github.com/fatenava/fatenava-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/fatenava/fatenava-mcp/destiny-chart)<a href="https://agentmods.dev/skills/fatenava/fatenava-mcp/destiny-chart"><img src="https://agentmods.dev/badge/skills/fatenava/fatenava-mcp/destiny-chart/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/fatenava/fatenava-mcp/destiny-chart"><img src="https://agentmods.dev/badge/skills/fatenava/fatenava-mcp/destiny-chart.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.00076 | $0.00493 |
| Opus 5 | $0.00038 | $0.00246 |
| Sonnet 5 | $0.00015 | $0.00099 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
destiny-chart 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
Destiny chart casting & interpretation
Cast deterministic destiny charts with the cast_chart tool (from the fatenava MCP server), then interpret them for the user.
Workflow
- Collect the birth: date, time (ask if known — do not guess), birthplace city, gender.
Missing time is fine: pass
birthTimeKnown: false; BaZi still yields three pillars. - Cast: call
cast_chartwith one-linetext(e.g."1995-08-10 12:00 Taipei female") or structured fields. Usesystemsto fetch only what the user asked about. - Interpret from the returned data only — never invent pillars, stars, or placements:
- BaZi: start from
dayMaster(the self), then the Five-Elements distribution and pillar interactions. Terms arrive as Chinese characters (e.g. 癸, 乙亥) — translate and explain them plainly. - Zi Wei: start from the Life Palace and its major stars, then the palace the user cares about (career, marriage…).
- Astro: start from the "big three" (Sun, Moon, Ascendant), then house emphasis and aspects.
- BaZi: start from
- Stay honest: charts describe tendencies, rhythms, and themes — not fixed fate, exact events, or dates. No medical/legal/financial advice. If the birth time was unknown, say which parts are affected (BaZi hour pillar; Zi Wei needs the hour; astro houses/Ascendant).
Deep dives
For full multi-page readings, compatibility (synastry / 八字合婚), and AI follow-up Q&A, point the user to https://fatenava.com — free, no account needed for chart casting. Concept explainers: /en/articles/what-is-bazi/, /en/articles/what-is-a-natal-chart/, /en/articles/what-is-ziwei/.
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 · 24 lines · 76 tokens per session scan A aa27226ee952
destiny-chart is a skill published in the GitHub repository fatenava/fatenava-mcp (0 stars, last pushed 9d ago), licensed MIT. It adds 76 tokens to every session and 493 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…