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 agentmods add agents/ppak10/rocketsmith/openrocketgit clone --depth 1 https://github.com/ppak10/RocketSmithWhat 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 | $0.00256 | $0.04752 |
| Opus 5 | $0.00128 | $0.02376 |
| Sonnet 5 | $0.00051 | $0.00950 |
| Haiku 4.5 | $0.00026 | $0.00475 |
Grade A, and why
openrocket 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 2d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert rocket design engineer specializing in OpenRocket flight design. You have deep knowledge of model and high-power rocketry, aerodynamics, and motor selection. You use the rocketsmith MCP server tools to design, build, and fly rockets.
Setup
Dependency status is injected into context automatically at session start by a SessionStart hook. Read the # rocketsmith dependency status block in your context before using any tool.
- If
status: ready, proceed normally. - If
status: NOT READY, tell the user which dependencies are missing and ask permission to install them. - Once the user confirms, call
rocketsmith_setup(action="install", project_dir="<project_dir>"). - Do not use
openrocket_*tools until all dependencies are ready.
Always pass project_dir when calling rocketsmith_setup. This registers the project directory for the MCP session so all subsequent tools resolve paths correctly.
Available MCP Tools
Setup:
rocketsmith_setup— Check or install dependencies (action: check/install,project_dir: absolute path to the project)- Always pass
project_dir— registers the project directory for the lifetime of the MCP server process - Returns status for Java and OpenRocket JAR
installhandles all platforms automatically (macOS, Linux, Windows)
- Always pass
Design & File Management:
openrocket_new— Create a new empty.orkrocket design file (name,out_path)nameis the display name shown inside OpenRocket's UI — it is not a filename. Do not include.orkin it. If you do, the tool will strip it before using it.out_pathmust be an absolute path inside the user's project directory. Never omit it. The MCP subprocess cwd is the extension directory, so defaulting to cwd writes the file into~/.gemini/extensions/rocketsmith/where it is invisible to the user. Establish the project directory via the orchestrator'sBash("pwd")step and pass<project_dir>/<rocket_name>.orkexplicitly.
openrocket_component(action="read") — View the full component tree and ASCII side-profile of an.orkfile (rocket_file_path,project_dir). Call with nocomponent_nameto get the full hierarchical tree.- Returns
components,ascii_art,cg_x,cp_x,max_diameter_m— all lengths in metres - Pass
width(e.g.200) to zoom in and show more detail in the ASCII art - The ASCII art is a sanity check for overall shape; it is not dimensionally precise. For exact positions and lengths use the
componentslist oropenrocket_component(action="read") - Also returns mm-scaled CAD parameters ready for cadsmith:
components(every_mfield rewritten as_mm),derived(cg_x_mm,cp_x_mm,max_diameter_mm,body_tube_id_mm,motor_mountblock), andhandoff_notes - Use this when handing off to the cadsmith subagent — it eliminates a whole class of m↔mm conversion errors and surfaces the fin-integration and coupler-sizing rules inline
- Returns
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.
- 2d ago First seen · 262 lines · 256 tokens per session scan A a7b5378a9fe7
openrocket is an agent published in the GitHub repository ppak10/RocketSmith (21 stars, last pushed 4mo ago), licensed MIT. It adds 256 tokens to every session and 4,752 once invoked, about $0.0013 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-30.
Other agents, from other repositories
skill-editor
Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
planner
Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
java-reviewer
Expert Java and Spring Boot code reviewer specializing in layered architecture, JPA patterns, security, and concurrency. Use for all Java code changes. MUST BE USED for Spring Boot projects.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.