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 model-lmn-boundarygit 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/model-lmn-boundary)<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/model-lmn-boundary"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/model-lmn-boundary.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.00079 | $0.01812 |
| Opus 5 | $0.00039 | $0.00906 |
| Sonnet 5 | $0.00016 | $0.00362 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
model-lmn-boundary 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model-based (Shue magnetopause) LMN boundary frame
Where boundary-minimum-variance derives the boundary normal from the field rotation
itself (MVA), this skill derives it from a model magnetopause (Shue et al.) evaluated
at the spacecraft position. The two are complementary: the model normal does not depend on
the field having a clean planar rotation, so it works where MVA fails (poor eigenvalue
separation) and gives an independent number to validate a trusted MVA normal against.
When to use
- "Give me an LMN normal that does NOT depend on the field rotation" (e.g. MVA eigenvalue ratio was too low to trust).
- "Rotate B into the model (Shue) magnetopause boundary-normal frame for this crossing."
- "Cross-check my MVA normal against the model magnetopause normal" — agreement strengthens the boundary identification.
Tool chain (all existing)
load_data_source → browse_data_parameters → fetch_data_product (B in GSM + spacecraft position)
→ build the (N,3,3) LMN matrix via the lmn_matrix_make backend (below)
→ apply it with the apply-rotation-matrix skill (tvector_rotate) → render_tplot,
all inside a create_spedas_analysis_bundle. Cross-reference boundary-minimum-variance
(data-driven LMN) and magnetopause-lmn-analysis (full field+plasma crossing study).
Backend (VERIFIED contract)
Two pyspedas functions, both operating on tplot variables — they STORE results, they do not return arrays:
pyspedas.cotrans_tools.lmn_matrix_make.lmn_matrix_make(pos_var_name, mag_var_name, trange=None, hro2=False, newname=None)- Inputs: names of two already-stored tplot variables —
pos_var_name(spacecraft position, GSM, (M,3)) andmag_var_name(B in GSM, (N,3)). Evaluates the Shue magnetopause model at the position to get the local normal and builds the L/M/N basis. - Returns: the name of a stored tplot variable holding the (N,3,3) LMN rotation-matrix stack — NOT the array. Retrieve the matrix with
get_data(<name>)→(times, (N,3,3) array). hro2=Trueselects the alternate (Shue 1998 vs. earlier) magnetopause parametrization;trangeclips the interval.
- Inputs: names of two already-stored tplot variables —
pyspedas.cotrans_tools.gsm2lmn.gsm2lmn(times, Rxyz, Bxyz, swdata=None)- Lower-level: takes raw arrays (
times, positionRxyz, fieldBxyz, optional solar-windswdata) and returns B rotated into LMN. The matrix path above plustvector_rotateis preferred (consistent withapply-rotation-matrix); usegsm2lmnonly when you already have the arrays in hand.
- Lower-level: takes raw arrays (
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.
- 7d ago First seen · 63 lines · 79 tokens per session scan A 0bde9ac626f5
model-lmn-boundary is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,812 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…
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…