magnetopause-lmn-analysis

magnetopause-lmn-analysis is a skill for Claude Code, Codex from spedas/spedas_agent_kit. It costs 82 tokens per session (1,227 once invoked), scanned A, original, MIT.

An end-to-end study of a magnetopause or bow-shock crossing using magnetic-field data, ion measurements, and spacecraft position. The magnetopause is the boundary between Earth’s magnetic field and the solar wind; a bow shock is the upstream shock wave formed by that interaction.

In plain words
What is it for?
Use it to screen for or characterize a boundary crossing, including its normal direction, rotated magnetic field, plasma jump, and spacecraft position.
Why use it?
It brings together the field direction, changes in plasma density and velocity, and spacecraft location to identify and check a crossing.

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 screen for or characterize a boundary crossing, including its normal direction, rotated magnetic field, plasma jump, and spacecraft position.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spedas/spedas_agent_kit/magnetopause-lmn-analysis
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 magnetopause-lmn-analysis
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 magnetopause-lmn-analysis

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/magnetopause-lmn-analysis"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/magnetopause-lmn-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,227 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.00082 $0.01227
Opus 5 $0.00041 $0.00613
Sonnet 5 $0.00016 $0.00245
Haiku 4.5 $0.00008 $0.00123

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

Security

Grade A, and why

magnetopause-lmn-analysis 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/magnetopause-lmn-analysis/SKILL.md · 53 lines

How it starts

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

Magnetopause / bow-shock crossing — full LMN study

The canonical SPEDAS boundary-crossing analysis, end to end. Where boundary-minimum-variance does the pure MVA step, this skill is the complete study: it pairs the field rotation with the plasma signature (density/velocity jump) and the spacecraft position that together identify the boundary and confirm the crossing.

When to use

  • "Screen for a magnetopause / bow-shock crossing near ."
  • "Characterize this boundary: normal, LMN field, plasma jump, where was the spacecraft?"
  • Any single-spacecraft current-sheet / discontinuity study needing field + plasma + geometry.

Tool chain (all existing)

search_spedas_data_sourcesplan_spedas_observationcreate_spedas_analysis_bundleload_data_sourcebrowse_data_parametersfetch_data_product (B and ion moments) → analyze_minvar_coordinatestransform_timeseries_coordinates (optional, Earth frames) → get_ephemeris / calculate_lshell (position) → render_tplot.

Procedure

  1. Plan & bundle. plan_spedas_observation(science_goal) to confirm source + a tight window around the crossing; create_spedas_analysis_bundle(...) for data/+plots/+provenance/. Keep the window short — one boundary, minutes not hours (the MMS example uses a 2-minute window).

  2. Pick datasets — field AND plasma. A boundary is identified by both the magnetic rotation and the plasma jump:

    • Magnetic field: the mission's FGM/MAG vector (confirm the variable with browse_data_parameters).
    • Ion moments: density, bulk velocity, temperature (e.g. FPI-DIS for MMS, SWE/3DP for Wind, SWEAP for PSP). Fetch each with fetch_data_product(source_type=..., dataset_id=..., parameters=[...], start, stop, output_dir=<bundle>/data). Check the returned stats/quality_checks before trusting the data.
  3. MVA on the field → boundary normal. analyze_minvar_coordinates(input_file=<B csv>, vector_cols=[Bx,By,Bz], output_dir=<bundle>/data). Gate on reliability: require λ_int/λ_min ≳ 5–10 before trusting the normal; report the ratio. (If the ratio is low, the window likely spans more than one structure — re-scope.)

Read the full file on GitHub · 53 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 · 53 lines · 82 tokens per session scan A c23c1f9230d5

Subscribe to this mod's changes

magnetopause-lmn-analysis is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 1,227 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.

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