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 spedas/spedas_agent_kit --skill psp-solo-heliophysics-workflowsgit clone --depth 1 https://github.com/spedas/spedas_agent_kitWrote 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/spedas/spedas_agent_kit/psp-solo-heliophysics-workflows)<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/psp-solo-heliophysics-workflows"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/psp-solo-heliophysics-workflows/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/spedas/spedas_agent_kit/psp-solo-heliophysics-workflows"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/psp-solo-heliophysics-workflows.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.00081 | $0.03049 |
| Opus 5 | $0.00041 | $0.01524 |
| Sonnet 5 | $0.00016 | $0.00610 |
| Haiku 4.5 | $0.00008 | $0.00305 |
Grade A, and why
psp-solo-heliophysics-workflows 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PSP / Solar Orbiter heliophysics workflows
Use this skill when the user asks for a Parker Solar Probe (PSP), Solar Orbiter (SolO), or inner-heliosphere solar-wind workflow and the request is broader than one narrow switchback reproduction. Typical prompts:
- "Plan PSP + Solar Orbiter radial-alignment analysis."
- "Which products should I load for PSP FIELDS/SWEAP and SolO MAG/SWA?"
- "Make a cache-friendly quicklook for a SolO switchback interval."
- "Compare PSP perihelion in-situ data with Solar Orbiter or Wind/ACE context."
- "Route a heliospheric workflow into Agent Kit resources without inventing tools."
This is a route-scout and load-plan skill, not a new MCP tool. The default
Agent Kit MCP surface stays compact: use spedas_overview,
search_spedas_data_sources, plan_spedas_observation, and
create_spedas_analysis_bundle first. External PySPEDAS loader names below are
runtime/library routes and must be labelled as such.
First decision
| User intent | Use this skill? | Compose with |
|---|---|---|
| PSP or SolO product/cadence/load-plan selection | Yes | pyspedas-load-planning, tplot-data-lifecycle |
| PSP/SolO radial alignment or conjunction context | Yes | spice-conjunction-finder, coordinate-frame-tour |
| PSP/SolO switchback / Alfvénic impulse reproduction | Yes for route scouting, then specialize | psp-solar-wind-switchbacks |
| PSP/SolO turbulence spectrum or PVI event table | Yes for products/cadence, then specialize | solar-wind-turbulence-spectrum, solar-wind-turbulence-intermittency |
| Stream interaction, ICME, storm, or wide heliosphere context | Usually yes as the inner-heliosphere branch | solar-wind-icme-storm, omni-kyoto-noaa-smoke-workflows |
| A pure archive-discovery question | Maybe | spedas_overview, search_spedas_data_sources, browse_data_sources |
MCP-first workflow
- Start with
spedas_overviewand confirm the compact default tool surface. - Call
search_spedas_data_sourcesorbrowse_data_sources(source_type="cdaweb")for candidate CDAWeb datasets. Do not assume a dataset ID without checking. - Use
browse_data_parameterson the selected dataset before choosing variable names. Record coordinate frame, cadence, units, and support variables. - For any real run, create an artifact/provenance workspace with
create_spedas_analysis_bundle. Do not paste arrays, CDF records, or tplot dumps into chat. Write small plots/tables/manifests to files. - If geometry matters, load
spice-conjunction-finderbefore source mapping or radial-alignment claims. Usecoordinate-frame-tourbefore mixing RTN, VSO, HCI/HAE/ECLIPJ2000, spacecraft-centered frames, or transformed vectors.
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 · 193 lines · 0 tokens per session scan A 9c6344dbfe6a
psp-solo-heliophysics-workflows is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 3,049 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
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…
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.
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…
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…