mms-basic-workflows

A routing guide for planning MMS spacecraft-data analyses, including magnetic fields, electric fields, plasma particles, spacecraft position, and wave measurements. MMS is a mission using four spacecraft to study Earth’s space environment and magnetic reconnection.

In plain words
What is it for?
Use it to plan MMS overviews, magnetic-reconnection studies, orbit context, electric-field or wave investigations, particle surveys, and four-spacecraft preparation.
Why use it?
It helps select suitable data products and analysis routes while preserving variable names, time ranges, plotting choices, and spacecraft-specific context.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/spedas/spedas_agent_kit/mms-basic-workflows
Any agent
npx skills add spedas/spedas_agent_kit --skill mms-basic-workflows
Clone the repo
git clone --depth 1 https://github.com/spedas/spedas_agent_kit

Made for: Claude Code, Codex.

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,824 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00043 $0.03824
Opus 5 $0.00022 $0.01912
Sonnet 5 $0.00009 $0.00765
Haiku 4.5 $0.00004 $0.00382

Measured yesterday against content hash 072a477e6a78, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mms-basic-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 yesterday.

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/mms-basic-workflows/SKILL.md · 306 lines

How it starts

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

MMS basic workflows

Use this skill when the user asks for an MMS mission overview, magnetic reconnection route scout, FGM/MEC orbit context, EDP electric-field/spacecraft-potential context, SCM wave context, FPI/HPCA particle overview, or MMS four-spacecraft preflight. This is a router skill: it connects MMS mission vocabulary to existing Agent Kit data/provenance tools, specialized analysis skills, and external PySPEDAS loaders without creating one MCP tool per MMS loader.

Compose it with:

  • pyspedas-load-planning for trange, probe, data_rate, level, datatype, time_clip=True, available=True, notplot, no_update, runtime CONFIG['download_only'], and run-scoped suffix hygiene.
  • tplot-data-lifecycle for variable naming, support-data choices, plotting, export, and cleanup without pasting arrays into chat.
  • spedas-heritage-vocabulary for IDL mms_load_* / PySPEDAS route translation.
  • spedas-workflow for existing MMS reconnection/EDR guardrails and the MMS magnetopause example; keep single-spacecraft current proxies labeled as proxies.
  • multi-spacecraft-gradients and dual-spacecraft-timing only after four MMS magnetic-field streams and four position streams pass cadence/frame checks.
  • magnetopause-lmn-analysis, boundary-minimum-variance, model-lmn-boundary, apply-rotation-matrix, and hodogram for LMN/MVA/FAC handoffs after a real boundary interval exists.
  • wave-polarization and power-spectral-density for SCM/FGM wave or spectral analysis; do not reimplement polarization logic here.
  • pitch-angle-distribution and particle-velocity-slice for particle products only when the exact FPI/HPCA distribution route, magnetic-field input, cadence, and calibration caveats are verified.

MCP/default-surface boundary

This skill adds no MCP tool. Keep the default Agent Kit list_tools surface compact. The names below are external PySPEDAS runtime routes, not Agent Kit MCP names:

external_runtime_route:
  not_an_mcp_tool: true
  examples:
    - pyspedas.projects.mms.fgm
    - pyspedas.projects.mms.mec
    - pyspedas.projects.mms.scm
    - pyspedas.projects.mms.fsm
    - pyspedas.projects.mms.fpi
    - pyspedas.projects.mms.hpca
    - pyspedas.projects.mms.edp
    - pyspedas.projects.mms.edi
    - pyspedas.projects.mms.eis
    - pyspedas.projects.mms.feeps
    - pyspedas.projects.mms.aspoc
    - pyspedas.projects.mms.dsp
    - pyspedas.projects.mms.bss
    - pyspedas.projects.mms.state
    - pyspedas.projects.mms.tetrahedron_qf
    - pyspedas.projects.mms.curlometer
    - pyspedas.projects.mms.lingradest
    - pyspedas.projects.mms.particles.mms_part_getspec.mms_part_getspec
    - pyspedas.projects.mms.particles.mms_part_slice2d.mms_part_slice2d
    - pyspedas.projects.mms.fpi_tools.mms_pad_fpi.mms_pad_fpi
    - pyspedas.projects.mms.fpi_tools.mms_load_fpi_calc_pad.mms_load_fpi_calc_pad

Read the full file on GitHub · 306 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. yesterday First seen · 306 lines · 43 tokens per session scan A 072a477e6a78

Subscribe to this mod's changes

mms-basic-workflows is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 29d ago), licensed MIT. It adds 43 tokens to every session and 3,824 once invoked, about $0.0002 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens