spice-conjunction-finder

spice-conjunction-finder is a skill for Claude Code, Codex from spedas/spedas_agent_kit. It costs 63 tokens per session (1,343 once invoked), scanned A, original, MIT.

A workflow for finding conjunctions, meaning times when two spacecraft or other bodies come close to each other. It compares their trajectories over a time interval, first roughly and then more precisely.

In plain words
What is it for?
Finding when two spacecraft are within a chosen distance, checking spacecraft–planet proximity, exporting ephemerides, refining candidate times, and optionally plotting separation over time.
Why use it?
It combines trajectory retrieval, distance calculations, and optional plotting to find close approaches without requiring one specialised tool to do everything.

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 Finding when two spacecraft are within a chosen distance, checking spacecraft–planet proximity, exporting ephemerides, refining candidate times, and optionally plotting separation over time.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spedas/spedas_agent_kit/spice-conjunction-finder
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 spice-conjunction-finder
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 spice-conjunction-finder

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/spedas/spedas_agent_kit/spice-conjunction-finder"><img src="https://agentmods.dev/badge/skills/spedas/spedas_agent_kit/spice-conjunction-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,343 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.00063 $0.01343
Opus 5 $0.00032 $0.00672
Sonnet 5 $0.00013 $0.00269
Haiku 4.5 $0.00006 $0.00134

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

Security

Grade A, and why

spice-conjunction-finder 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/spice-conjunction-finder/SKILL.md · 56 lines

How it starts

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

Multi-spacecraft / body conjunction finder

A guided version of the SPEDAS conjunction crib: locate the times in a window when two objects (two spacecraft, or a spacecraft and a planet) are within some separation. The value is the scan-and-refine procedure with kernel handling — no single tool finds conjunctions; this composes the geometry tools with a small local separation calculation and judgment between steps.

When to use

  • "When were PSP and Solar Orbiter closest in ?"
  • "Find conjunctions between and under million km."
  • "Is spacecraft X near planet Y during this interval?"

Tool chain (all already exist)

spedas_overview()manage_data_cache(source_type="spice", action="status") (availability) → get_ephemeris(target=..., time=..., time_end=..., output_file=...) for both objects → local separation CSV (coarse, then refined) → optional render_tplot (requires spedas-agent-kit[analysis]), wrapped in create_spedas_analysis_bundle.

compute_distance(...) is useful as a quick sanity check for aggregate min/max/mean separation over a sampled interval, but it currently does not return the timestamp of the minimum or a sampled series. Do not use it as the source of candidate-minimum times.

Procedure

  1. Bundle. create_spedas_analysis_bundle(study_name, output_dir, science_goal, start, stop).

  2. Confirm the SPICE surface and target names. Start with spedas_overview() and manage_data_cache(source_type="spice", action="status") to confirm the current unified geometry/data surface. The older separate mission/frame listing tools are not part of the current advertised surface. Use supported target/frame names accepted by get_ephemeris/compute_distance (unsupported bodies return a structured unsupported_spice_target error with alternatives; unsupported frames return a structured frame error). Pick one observer and frame for both trajectories, normally observer="SUN" and frame="ECLIPJ2000" unless the science case requires otherwise.

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

Subscribe to this mod's changes

spice-conjunction-finder is a skill published in the GitHub repository spedas/spedas_agent_kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,343 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.

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