What is gmat-improve?

A checked workflow for improving GMAT scripts, which are text files used to model and simulate spacecraft missions. It runs the original script, diagnoses problems, applies fixes, and runs it again.

Use it to fix, review, modernize, make portable, or adapt GMAT mission scripts, including scripts intended to run without a graphical interface.

It helps distinguish a real script failure from an unintended change by comparing each revision with a working baseline.

gmat-improve — Skill for Claude Code and Codex by ginomoretta-creator

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 ginomoretta-creator/gmat-mcp-server --skill gmat-improve

Clone the repo

git clone --depth 1 https://github.com/ginomoretta-creator/gmat-mcp-server

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ginomoretta-creator/gmat-mcp-server/gmat-improve/github.svg)](https://agentmods.dev/skills/ginomoretta-creator/gmat-mcp-server/gmat-improve)

Your own site

<a href="https://agentmods.dev/skills/ginomoretta-creator/gmat-mcp-server/gmat-improve"><img src="https://agentmods.dev/badge/skills/ginomoretta-creator/gmat-mcp-server/gmat-improve/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ginomoretta-creator/gmat-mcp-server/gmat-improve"><img src="https://agentmods.dev/badge/skills/ginomoretta-creator/gmat-mcp-server/gmat-improve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 894 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.

Model	Per session	Once invoked
Fable 5.1	$0.00110	$0.00894
Opus 5	$0.00055	$0.00447
Sonnet 5	$0.00022	$0.00179
Haiku 4.5	$0.00011	$0.00089

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

Security

Grade A, and why

gmat-improve 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 11d 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.

skills/gmat-improve/SKILL.md · 59 lines

How it starts

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

GMAT script improvement loop

You improve a script the same way you'd review a colleague's mission design: first make sure you understand what it intends to do, then verify what it actually does, then change one thing at a time with a re-run after each change. Never deliver an edited script you haven't re-run.

The loop

Establish intent. Read the script and write one paragraph: mission type, spacecraft, force model, maneuvers, what the targeters/optimizers are solving for, what the outputs should be. If intent is ambiguous, ask the user before changing behavior.
Baseline run. runGmat the script untouched. Record: stage, errors, report values, wall time (from the result). This baseline is your regression test — every improvement must either preserve these numbers (within tolerance) or change them for an explained, intended reason.
Diagnose against the known failure catalog. Call getGmatIdioms and check the script against it. The highest-frequency offenders in real community scripts, in order:
- Hardcoded absolute paths in ReportFile.Filename, SPICE kernels, gravity files — the #1 portability killer. Rewrite report filenames to bare names; flag missing data files to the user rather than guessing replacements.
- Non-ASCII characters (accented comments break the whole parse).
- Hardcoded burn values that should be targeted (Maneuver with magic numbers and no Target block — fragile to any upstream change).
- Stop conditions that fail on circular orbits (apsides) or cumulative-ElapsedSecs bugs.
- Tight Achieve tolerances on osculating elements under J2.
- GUI subscribers (OrbitView, XYPlot) in scripts meant to run headless — harmless in console mode but noise; keep them only if the user uses the GUI.
- Unthrottled ReportFile on long propagations (megabytes of substeps).
- While/If with compound &/| guards or parentheses (unreliable / parse error).

Read the full file on GitHub · 59 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.

11d ago First seen · 59 lines · 110 tokens per session scan A 6dc9585352c4

Subscribe to this mod's changes

gmat-improve is a skill published in the GitHub repository ginomoretta-creator/gmat-mcp-server (2 stars, last pushed 3mo ago), licensed ISC. It adds 110 tokens to every session and 894 once invoked, about $0.0006 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.

Debugging Scientific

trace

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.

Yeachan-Heo/oh-my-claudecode · 18 tokens

smiles-validation

Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.

synthetic-sciences/openscience · 24 tokens

social-physics-filter

Unified boundary enforcement, interpersonal diagnostic, and relational audit engine. Absorbs 40 psychology + 2 social protocols and all relationship case studies.

winstonkoh87/Athena-Public · 34 tokens

cnsplots

Create, revise, and troubleshoot publication-ready scientific plots in Python with cnsplots, including distribution, regression, heatmap, genomics, survival, set, flow, and multi-panel figures. Use when a user asks for cnsplots code, Cell/Nature/Science-style visualization, precise physical figure dimensions…

faridrashidi/cnsplots · 79 tokens

relax-dev-debug

Develop and debug the Relax reinforcement learning project. Use this skill whenever modifying code in the relax/ directory, or running remote training jobs on a Ray cluster for validation. Also use it when the user mentions training, debugging training runs, submitting Ray jobs, or fixing training errors.

redai-infra/Relax · 60 tokens

anomaly-characterization

SOP: Describe and classify anomalous phenomena that existing theory cannot explain.

yogsoth-ai/de-anthropocentric-research-engine · 19 tokens