exoplanet-workflows

exoplanet-workflows is a skill for Claude Code, Codex from xuansenpa1/skillrevise. It costs 45 tokens per session (1,526 once invoked), scanned A, a copy of exoplanet-workflows, MIT.

A set of workflows for finding and studying possible exoplanets, planets outside our solar system, in light-curve data that records how a star’s brightness changes over time.

In plain words
What is it for?
It helps plan data loading, quality checks, noise removal, period searches, candidate validation, and parameter estimation.
Why use it?
It helps organize the analysis so noise, faulty measurements, and false signals are separated from possible planet transits.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps plan data loading, quality checks, noise removal, period searches, candidate validation, and parameter estimation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xuansenpa1/skillrevise/exoplanet-workflows
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 xuansenpa1/skillrevise --skill exoplanet-workflows
Clone the repo
git clone --depth 1 https://github.com/xuansenpa1/skillrevise

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 exoplanet-workflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/exoplanet-workflows/github.svg)](https://agentmods.dev/skills/xuansenpa1/skillrevise/exoplanet-workflows)
Your own site
<a href="https://agentmods.dev/skills/xuansenpa1/skillrevise/exoplanet-workflows"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/exoplanet-workflows/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 exoplanet-workflows

Your own site · 80×15
<a href="https://agentmods.dev/skills/xuansenpa1/skillrevise/exoplanet-workflows"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/exoplanet-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,526 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 100% copy Near-identical to another mod 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.00045 $0.01526
Opus 5 $0.00023 $0.00763
Sonnet 5 $0.00009 $0.00305
Haiku 4.5 $0.00005 $0.00153

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

Security

Grade A, and why

exoplanet-workflows 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 10d 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.

Origin

This is a copy

100% identical to exoplanet-workflows — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

data/skillsbench/tasks/exoplanet-detection-period/environment/skills/exoplanet-workflows/SKILL.md · 204 lines

How it starts

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

Exoplanet Detection Workflows

This skill provides general guidance on exoplanet detection workflows, helping you choose the right approach for your data and goals.

Overview

Exoplanet detection from light curves typically involves:

  1. Data loading and quality control
  2. Preprocessing to remove instrumental and stellar noise
  3. Period search using appropriate algorithms
  4. Signal validation and characterization
  5. Parameter estimation

Pipeline Design Principles

Key Stages

  1. Data Loading: Understand your data format, columns, time system
  2. Quality Control: Filter bad data points using quality flags
  3. Preprocessing: Remove noise while preserving planetary signals
  4. Period Search: Choose appropriate algorithm for signal type
  5. Validation: Verify candidate is real, not artifact
  6. Refinement: Improve period precision if candidate is strong

Critical Decisions

What to preprocess?

  • Remove outliers? Yes, but not too aggressively
  • Remove trends? Yes, stellar rotation masks transits
  • How much? Balance noise removal vs. signal preservation

Which period search algorithm?

  • TLS: Best for transit-shaped signals (box-like dips)
  • Lomb-Scargle: Good for any periodic signal, fast exploration
  • BLS: Alternative to TLS, built into Astropy

What period range to search?

  • Consider target star type and expected planet types
  • Hot Jupiters: short periods (0.5-10 days)
  • Habitable zone: longer periods (depends on star)
  • Balance: wider range = more complete, but slower

When to refine?

  • After finding promising candidate
  • Narrow search around candidate period
  • Improves precision for final measurement

Choosing the Right Method

Transit Least Squares (TLS)

Use when:

  • Searching for transiting exoplanets
  • Signal has transit-like shape (box-shaped dips)
  • You have flux uncertainties

Advantages:

  • Most sensitive for transits
  • Handles grazing transits
  • Provides transit parameters

Disadvantages:

  • Slower than Lomb-Scargle
  • Only detects transits (not RV planets, eclipsing binaries with non-box shapes)

Read the full file on GitHub · 204 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. 10d ago First seen · 204 lines · 45 tokens per session scan A 5ebc27240999

Subscribe to this mod's changes

exoplanet-workflows is a skill published in the GitHub repository xuansenpa1/skillrevise (56 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 1,526 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to exoplanet-workflows, differing in 0 lines, and is treated as a copy.

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

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

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

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