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 spectral-cross-coherencegit 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/spectral-cross-coherence)<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/spectral-cross-coherence"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/spectral-cross-coherence/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/spectral-cross-coherence"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/spectral-cross-coherence.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.00065 | $0.01946 |
| Opus 5 | $0.00032 | $0.00973 |
| Sonnet 5 | $0.00013 | $0.00389 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
spectral-cross-coherence 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 8d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spectral cross-coherence and cross-phase
The two-channel companion to the single-channel power-spectral-density workflow
(solar-wind-turbulence-spectrum). From two scalar time series over the same
interval, compute the magnitude-squared coherence C_xy(f) ∈ [0,1] (how
linearly related the two channels are at each frequency) and the cross-phase
∠P_xy(f) (the phase lag between them). This is how you ask whether two signals
share a common wave at frequency f, and which one leads — e.g. B_R vs B_T,
B vs density (compressional vs incompressible), or the same channel on two
spacecraft for propagation timing.
When to use
- "Are these two channels coherent at frequency f, and what's the phase lag?"
- "Is this fluctuation compressional?" — coherence/phase between |B| and density.
- Wave-mode / propagation: phase lag between two components, or the same field on two spacecraft.
Tool chain (existing tools only)
create_spedas_analysis_bundle → load_data_source → browse_data_parameters
→ fetch_data_product (×2, or one multi-component fetch + derive the two scalars)
→ local scipy coherence/csd on a common uniform time grid → write per-panel .npz
→ render_tplot. There is no dedicated pyspedas coherence tool — the spectral step is a
small local computation, the same pattern as the local PSD step in the turbulence skill.
Backend (VERIFIED contract)
There is no MCP/pyspedas cross-coherence tool; you compute it locally with scipy
and persist .npz artifacts. The verified numeric contract:
- Input is a state array, not a stored tplot var: scipy works on plain in-memory
ndarrays
x,ythat you have already loaded from the fetched files and resampled to one common uniform time grid. Coherence requires identical sampling — samefs, same length, sample-aligned — so both channels must be interpolated onto the same numeric Unix-second grid before this step. There is no tplot variable and no dict/tuple handed back by a tool here. scipy.signal.coherence(x, y, fs=fs, nperseg=...)→ returns a plain tuple(f, Cxy):f= frequency ndarray,Cxy= magnitude-squared coherence ndarray in [0,1]. Welch-averaged over segments.scipy.signal.csd(x, y, fs=fs, nperseg=...)→ returns(f, Pxy):Pxyis the complex cross-spectral density. Cross-phase =numpy.angle(Pxy)(rad); convert to degrees for the panel:numpy.degrees(numpy.angle(Pxy)).- Both calls return plain ndarrays computed locally (same as the pwrspc-style PSD step); nothing is stored as a tplot variable.
render_tplot= ONE 2-D matrix per.npz. A coherence-vs-frequency curve and a phase-vs-frequency curve are two separate panels, so write one.npzper panel (do not pack both into one multi-key file and expect a 2-panel stack). Keep them side-by-side on the same frequency axis.
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.
- 8d ago First seen · 94 lines · 65 tokens per session scan A ac6191996075
spectral-cross-coherence is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,946 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.
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…