Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mayank-io/mstack/plugin install fetchWrote 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/mayank-io/mstack/vedic-chart)<a href="https://agentmods.dev/skills/mayank-io/mstack/vedic-chart"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/vedic-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/mayank-io/mstack/vedic-chart"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/vedic-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.00131 | $0.01126 |
| Opus 5.5 | $0.00052 | $0.00450 |
| Sonnet 5.5 | $0.00026 | $0.00225 |
| Haiku 4.5 | $0.00013 | $0.00113 |
Grade A, and why
vedic-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 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vedic Chart Extractor
Convert a Vedic astrology chart image (a Jagannatha Hora / Parashara's Light style printout) into a structured JSON chart and ASCII North-Indian + South-Indian diagrams. A bundled script does the work end to end.
What the source images look like
The script targets the standard software printout: a North-Indian chart (left), a
South-Indian chart (right), a birth-data header, and — crucially — a longitude
table across the bottom listing each body as sign deg' min with retrograde and
Jaimini karaka markers (e.g. Su: 4 Sc 08-DK). That bottom table is the ground
truth; houses are computed from it deterministically, so the chart diagrams are
never parsed glyph-by-glyph.
A chart-only image with no bottom table still works, but bodies the table would have carried fall back to sign-only placement (no degrees).
How it works
image --(claude vision reads the longitude table)--> chart JSON --(pure renderers)--> ASCII
House placement is house = (sign_index - lagna_index) mod 12 + 1. North-Indian is
house-fixed (Lagna always top-center, signs rotate); South-Indian is sign-fixed
(Pisces/Aries/… in fixed cells, houses rotate). Both render from the same JSON.
Usage
Extraction calls the claude CLI (must be on PATH, recent enough to accept
--effort and --allowedTools). Run the bundled script:
# extract + render both ASCII styles; JSON then charts to stdout
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/chart_to_ascii.py path/to/chart.png
# write sidecars (<stem>.json + <stem>.txt) next to the image(s)
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/chart_to_ascii.py images/*.png -o images/
# render only, no vision call, from a previously extracted JSON
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/chart_to_ascii.py chart.json --emit ascii
Options: --emit {json,ascii,both} (default both), --style {north,south,both}
(default both), -o/--outdir DIR, --model MODEL (default claude-opus-4-8),
--overwrite (re-extract even if a sibling .json exists; otherwise a cached
sidecar is reused). Data goes to stdout, progress/errors to stderr, non-zero exit
on any failure.
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 · 89 lines · 131 tokens per session scan A 1cfbc811a42c
vedic-chart is a skill published in the GitHub repository mayank-io/mstack (6 stars, last pushed 3d ago), licensed MIT. It adds 131 tokens to every session and 1,126 once invoked, about $0.0005 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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.