pitch-angle-distribution

pitch-angle-distribution is a skill for Claude Code, Codex from spedas/spedas_agent_kit. It costs 81 tokens per session (2,232 once invoked), scanned A, original, MIT.

A field-aligned view of a particle population showing how many particles have different angles to the local magnetic field. It can reveal beams, pancake-shaped distributions, isotropic populations, or loss cones.

In plain words
What is it for?
Use it to create pitch-angle spectrograms for electrons or ions, classify the population, and check for particles missing near particular field-aligned directions.
Why use it?
It turns a three-dimensional particle distribution into a plot that makes its direction relative to the magnetic field easier to interpret.

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 create pitch-angle spectrograms for electrons or ions, classify the population, and check for particles missing near particular field-aligned directions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spedas/spedas_agent_kit/pitch-angle-distribution
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 pitch-angle-distribution
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 pitch-angle-distribution

README.md
[![agentmods](https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/pitch-angle-distribution/github.svg)](https://agentmods.dev/skills/spedas/spedas_agent_kit/pitch-angle-distribution)
Your own site
<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.

agentmods 80×15 button for pitch-angle-distribution

Your own site · 80×15
<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>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,232 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.00081 $0.02232
Opus 5 $0.00041 $0.01116
Sonnet 5 $0.00016 $0.00446
Haiku 4.5 $0.00008 $0.00223

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

Security

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.

.agents/plugins/spedas-codex/skills/pitch-angle-distribution/SKILL.md · 63 lines

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 with build_particle_distribution_artifact (convert a 3D distribution you already have) or load_particle_distribution_artifact (the #95 bridge: fetch/load + convert in one step). Both write the file and return its path; pass that path as dist_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= or magf=) and stores it as embedded magf shaped (T,3). compute_particle_spectra(spectrum_types=["pitch_angle"]) reuses that embedded magf automatically — no separate mag_file needed. The pitch-angle entry reports mag_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_file is an optional override. Pass mag_file only 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 key b as (T,3) (one B vector per distribution slice) or (3,) (broadcast), in the distribution's own coordinate frame. An explicit mag_file wins over embedded magf; the entry then reports mag_source: "mag_file".
  • needs_input, not failure. spectrum_types defaults to ["energy","pitch_angle"]. "pitch_angle" needs a B reference: embedded magf or mag_file. Only when the artifact has no embedded magf and no mag_file is passed does the pitch-angle entry return status: "needs_input" (code needs_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>.npz as a single (n_time, n_bin) 2-D matrix (here n_bin = pitch-angle bins, axis 0–180°). The tool returns paths + ranges + shapes only, never the arrays. render_tplot then renders exactly one matrix per .npz as a pcolormesh panel.

Read the full file on GitHub · 63 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 · 63 lines · 81 tokens per session scan A cd07dadd6e83

Subscribe to this mod's changes

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.

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