overview-geomagnetic-indices

overview-geomagnetic-indices is a skill for Claude Code, Codex from spedas/spedas_agent_kit. It costs 62 tokens per session (3,149 once invoked), scanned A, original, MIT.

A guide for choosing datasets and parameters for standard spacecraft overview plots and geomagnetic indices. These indices, including Dst, AE, Kp, and SYM-H, summarize disturbances in Earth’s magnetic environment.

In plain words
What is it for?
Use it to plan overview plots for THEMIS, MMS, or RBSP data, or to retrieve Dst, AE/AL/AU, Kp, and SYM-H values for a selected time interval.
Why use it?
It helps translate a broad request for space-weather context into specific data sources and measurements.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to plan overview plots for THEMIS, MMS, or RBSP data, or to retrieve Dst, AE/AL/AU, Kp, and SYM-H values for a selected time interval.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spedas/spedas_agent_kit/overview-geomagnetic-indices
Install

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.

Any agent
npx skills add spedas/spedas_agent_kit --skill overview-geomagnetic-indices
Clone the repo
git clone --depth 1 https://github.com/spedas/spedas_agent_kit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for overview-geomagnetic-indices

README.md
[![agentmods](https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/overview-geomagnetic-indices/github.svg)](https://agentmods.dev/skills/spedas/spedas_agent_kit/overview-geomagnetic-indices)
Your own site
<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/overview-geomagnetic-indices"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/overview-geomagnetic-indices/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.

agentmods 80×15 button for overview-geomagnetic-indices

Your own site · 80×15
<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/overview-geomagnetic-indices"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/overview-geomagnetic-indices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.03149
Opus 5 $0.00031 $0.01574
Sonnet 5 $0.00012 $0.00630
Haiku 4.5 $0.00006 $0.00315

Measured 9d ago against content hash 421570f2e0f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

overview-geomagnetic-indices 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 9d 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.

.agents/plugins/spedas-codex/skills/overview-geomagnetic-indices/SKILL.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview recipes + geomagnetic indices

Use this skill when the user asks for a standard summary/overview plot (IDL-SPEDAS style thm_gen_overplot / mms_overview_plot) or for common geomagnetic indices (Dst, AE/AL/AU, Kp, SYM-H) to contextualize a near-Earth interval.

This is intentionally an intent-to-dataset/parameter recipe, not a new backend. Plan first, then use the existing unified data layer and HAPI tools.

MCP/default-surface boundary

Treat pyspedas... loader names in this skill as external runtime routes, not Agent Kit MCP tool names (external_runtime_route.not_an_mcp_tool: true). MCP-only clients should call spedas_overview() and follow each guided_recipes.geomagnetic_indices[*].mcp_first_route before trying local Python. Those MCP-first routes use browse_data_sources, load_data_source, browse_data_parameters, and fetch_data_product against CDAWeb candidates:

  • Dst: OMNI2_H0_MRG1HR, browse Dst.
  • AE/AL/AU: OMNI_HRO_1MIN, OMNI_HRO2_1MIN, or OMNI2_H0_MRG1HR, browse AE_INDEX, AL_INDEX, and AU_INDEX.
  • Kp/ap: OMNI2_H0_MRG1HR, browse Kp and ap.
  • SYM-H/SYM-D/ASY-H/ASY-D: OMNI_HRO_1MIN or OMNI_HRO2_1MIN, browse the named parameters.

Use direct Kyoto/NOAA/GOES PySPEDAS loaders only when the surrounding runtime can import PySPEDAS and run local scripts; otherwise report the external-runtime requirement instead of inventing MCP tool names.

First calls

  1. spedas_overview() — confirms the current recipe catalog.
  2. plan_spedas_observation(science_goal=..., start=..., stop=...) — infer target, time range, and recommended source types.
  3. For mission data: use browse_data_sources(source_type="cdaweb", query=<mission>), load_data_source(source_type="cdaweb", source_id=<observatory>), then browse_data_parameters(source_type="cdaweb", dataset_id=<dataset_id>) before fetching.
  4. For HAPI OMNI context: start with browse_data_sources(source_type="hapi") and follow its next_tools to browse_hapi_catalog(server_url="https://cdaweb.gsfc.nasa.gov/hapi", query="OMNI_HRO"), then fetch_hapi_data(...) with the dataset/parameters below. The direct HAPI tools are demoted out of the default list_tools surface (issue #87); reach them via that discovery route or set SPEDAS_AGENT_KIT_DATASOURCE_TOOLS=1. HAPI support requires the optional spedas-agent-kit[hapi] extra; if unavailable, fall back to CDAWeb discovery for the same OMNI dataset IDs.

Read the full file on GitHub · 176 lines

Changes

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.

  1. 9d ago First seen · 176 lines · 62 tokens per session scan A 421570f2e0f7

Subscribe to this mod's changes

overview-geomagnetic-indices is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 3,149 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.

Related

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…

anthropics/knowledge-work-plugins · 123 tokens

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…

K-Dense-AI/scientific-agent-skills · 83 tokens

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.

K-Dense-AI/scientific-agent-skills · 42 tokens

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.

K-Dense-AI/scientific-agent-skills · 68 tokens

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.

davila7/claude-code-templates · 43 tokens

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…

maziyarpanahi/openmed · 205 tokens