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 pitch-angle-distributiongit 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/pitch-angle-distribution)<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/pitch-angle-distribution"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/pitch-angle-distribution/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/pitch-angle-distribution"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/pitch-angle-distribution.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.02232 |
| Opus 5 | $0.00041 | $0.01116 |
| Sonnet 5 | $0.00016 | $0.00446 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
pitch-angle-distribution 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.
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.
Field-aligned pitch-angle distribution (PAD)
A guided version of the IDL SPEDAS particle pitch-angle crib sheet — take a particle
population over an interval and ask the classic question: is it a beam, a pancake, or
isotropic, and is there a loss cone? Pitch angle is the angle between the particle
velocity and the local magnetic field, so the whole workflow hinges on having a B field
to define the field-aligned axis. There is no dedicated "PAD" tool and there should not
be: compute_particle_spectra already produces the field-aligned 0–180° spectrum
directly. This skill is the procedure and interpretation wrapped around it.
When to use
- "Is this electron/ion population a beam, a pancake, or isotropic?"
- "Show me the pitch-angle distribution / PAD for on ."
- "Is there a loss cone in this interval?" (the field-aligned-vs-perpendicular question PADs exist to answer.)
Tool chain (all already exist)
create_spedas_analysis_bundle →
(build_particle_distribution_artifact | load_particle_distribution_artifact, the #95 bridge — give it the B field here via mag_tplot_name=/magf=) →
compute_particle_spectra(spectrum_types=["pitch_angle"]) (reuses the artifact's embedded magf) →
render_tplot.
Backend (VERIFIED contract)
- Distribution input.
compute_particle_spectra(dist_file, output_dir, ...)reads a distribution artifact on disk — not an in-memory array and not a stored tplot variable name. Produce that artifact withbuild_particle_distribution_artifact(convert a 3D distribution you already have) orload_particle_distribution_artifact(the #95 bridge: fetch/load + convert in one step). Both write the file and return its path; pass that path asdist_file. - B field comes from the artifact by default (issue #148). The #95 bridge already requires a B field to write the artifact (
mag_tplot_name=ormagf=) and stores it as embeddedmagfshaped(T,3).compute_particle_spectra(spectrum_types=["pitch_angle"])reuses that embeddedmagfautomatically — no separatemag_fileneeded. The pitch-angle entry reportsmag_source: "distribution_artifact_magf". This B defines the field-aligned +z; each slice is rotated into FAC (spd_pgs_do_fac) and the polar/pitch angle is binned over 0–180° (colatitude mode). mag_fileis an optional override. Passmag_fileonly when you want a different B reference than the one embedded in the artifact (e.g. a higher-cadence or differently-framed magnetometer product). It is a separate file (.npz/.json), not a tplot var, holding keybas(T,3)(one B vector per distribution slice) or(3,)(broadcast), in the distribution's own coordinate frame. An explicitmag_filewins over embeddedmagf; the entry then reportsmag_source: "mag_file".- needs_input, not failure.
spectrum_typesdefaults to["energy","pitch_angle"]."pitch_angle"needs a B reference: embeddedmagformag_file. Only when the artifact has no embeddedmagfand nomag_fileis passed does the pitch-angle entry returnstatus: "needs_input"(codeneeds_input,mag_source: "missing") while any other requested spectra still compute — the call does not hard-fail. - Output = one matrix per .npz, artifact-first. Each spectrogram is written to
output_dir/particle_spectra_<type>.npzas a single(n_time, n_bin)2-D matrix (heren_bin= pitch-angle bins, axis 0–180°). The tool returns paths + ranges + shapes only, never the arrays.render_tplotthen renders exactly one matrix per.npzas a pcolormesh panel.
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.
- 9d ago First seen · 63 lines · 81 tokens per session scan A cd07dadd6e83
pitch-angle-distribution 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 2,232 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…