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 adityarya24/astro-skill --skill astrogit clone --depth 1 https://github.com/adityarya24/astro-skillWrote 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/adityarya24/astro-skill/astro)<a href="https://agentmods.dev/skills/adityarya24/astro-skill/astro"><img src="https://agentmods.dev/badge/skills/adityarya24/astro-skill/astro.svg" alt="Measured on agentmods" 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.00054 | $0.01408 |
| Opus 5 | $0.00027 | $0.00704 |
| Sonnet 5 | $0.00011 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
astro 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 6d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro Skill
Use this skill to calculate and explain Vedic astrology outputs. Keep responses practical, respectful, and grounded in computed data. Do not predict death, accidents, medical diagnoses, or unavoidable harm.
Defaults
- Ayanamsa: Lahiri Chitrapaksha.
- House system: whole sign.
- Default language: Hinglish (
hin), with Hindi (hi) and English (en) supported by callers. - Default location for non-birth daily work: Delhi, India.
Required Inputs
- Kundali: date of birth, time of birth, place, latitude, longitude, timezone.
- Dasha: kundali output from
kundali_calculator.py. - Panchang: local date, place, latitude, longitude, timezone.
- Basic report: kundali JSON, with optional dasha JSON and panchang JSON.
- PDF report: kundali JSON plus optional dasha and panchang JSON; dasha is recommended for the timeline chart.
- Gochar (transits): kundali JSON plus a local calendar date (and optional place for location-sensitive work).
- Guna Milan: two complete kundali JSON files (both people need full birth details).
- Muhurta and other advanced modules may require purpose plus date range when implemented.
Phase 1 Workflow
- Run
scripts/kundali_calculator.pywith birth details and--json. - Inspect
lagna,rashi,nakshatra,nakshatra_pada,planets,houses, anddasha_seed. - Run
scripts/dasha_calculator.py --kundali-json <path> --jsonwhen dasha timing is needed. - Explain the output in the user's preferred language/tone. Mention calculations and practical meaning; avoid mystical filler.
Phase 2 Workflow
- Run
scripts/panchang_calculator.pywith local date, place, latitude, longitude, timezone, and--json. - Inspect
vara,tithi,paksha,nakshatra,yoga,karana,sunrise, andsunset. - Use the Panchang output as calculation data for daily guidance or later muhurta work. Do not convert it into muhurta recommendations unless a muhurta module is available.
- If sunrise or sunset is
null, check thewarningsarray and explain that the rest of the Panchang fields still came from computed solar/lunar positions.
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 179 B
- assets/cover_ganesha.png 287 KB
- config/defaults.json 299 B
- data/ashtakavarga_data.json 2.7 KB
- data/avakahada_data.json 5.9 KB
- data/compatibility_data.json 2.1 KB
- data/functional_nature.json 2.7 KB
- data/gochar_narrative_data.json 15 KB
- data/graha_data.json 5.2 KB
- data/nakshatra_db.json 3.4 KB
- data/personality_ext.json 8.5 KB
- data/phalit_basic.json 14 KB
- data/phalit_ext.json 27 KB
- data/remedies_ext.json 4.2 KB
- data/remedies.json 15 KB
- ephe/README.md 1.2 KB
- ephe/semo_18.se1 1274 KB
- ephe/sepl_18.se1 473 KB
- scripts/__init__.py 66 B runs code
- scripts/ashtakavarga.py 1.7 KB runs code
- scripts/aspects.py 2.0 KB runs code
- scripts/avakahada.py 3.5 KB runs code
- scripts/dasha_calculator.py 7.1 KB runs code
- scripts/fonts/NotoSansDevanagari.ttf 632 KB
- scripts/gochar_calculator.py 6.7 KB runs code
- scripts/gochar_narrative.py 14 KB runs code
- scripts/guna_milan.py 7.8 KB runs code
- scripts/kundali_calculator.py 22 KB runs code
- scripts/panchang_calculator.py 16 KB runs code
- scripts/pdf_report.py 34 KB runs code
- scripts/remedies.py 1.1 KB runs code
- scripts/report_generator.py 12 KB runs code
- scripts/swe_lock.py 1.1 KB runs code
- scripts/vargas.py 2.1 KB runs code
- scripts/yoga_detector.py 16 KB runs code
- tests/test_ashtakavarga.py 1.6 KB runs code
- tests/test_aspects.py 1.7 KB runs code
- tests/test_astro_mcp_server.py 3.9 KB runs code
- tests/test_astro_mcp_storage.py 4.9 KB runs code
- tests/test_astro_mcp_tools.py 9.4 KB runs code
- tests/test_avakahada.py 1.9 KB runs code
- tests/test_ayanamsa.py 1.5 KB runs code
- tests/test_dasha_balance_antardasha.py 3.2 KB runs code
- tests/test_dasha.py 4.4 KB runs code
- tests/test_gochar_narrative.py 6.9 KB runs code
- tests/test_gochar.py 2.5 KB runs code
- tests/test_guna_milan.py 3.6 KB runs code
- tests/test_kundali.py 5.1 KB runs code
- tests/test_panchang.py 3.9 KB runs code
- tests/test_parse_birth_details_time.py 2.2 KB runs code
- tests/test_pdf_report_escaping.py 1.9 KB runs code
- tests/test_pdf_report.py 4.7 KB runs code
- tests/test_planetary_strength.py 8.2 KB runs code
- tests/test_pratyantardasha.py 2.1 KB runs code
- tests/test_project_structure.py 3.3 KB runs code
- tests/test_remedies.py 3.4 KB runs code
- tests/test_report.py 7.0 KB runs code
- tests/test_smoke_mcp_script.py 1.1 KB runs code
- tests/test_vargas.py 2.0 KB runs code
- tests/test_yoga.py 13 KB runs code
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.
- 6d ago First seen · 94 lines · 54 tokens per session scan A bd7a600d7de7
astro is a skill published in the GitHub repository adityarya24/astro-skill (1 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 1,408 once invoked, about $0.0003 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…