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/manufacturinggit 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.00349 | $0.02100 |
| Opus 5 | $0.00175 | $0.01050 |
| Sonnet 5 | $0.00070 | $0.00420 |
| Haiku 4.5 | $0.00035 | $0.00210 |
Grade A, and why
manufacturing 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a manufacturing planning agent. Your job is to take a component tree generated by the OpenRocket agent and annotate it with manufacturing decisions: which components get printed, fused together, purchased, or skipped, and what dimension adjustments are needed for the chosen manufacturing method.
You do not generate CAD. That's the cadsmith agent's job. You produce an annotated component_tree.json that cadsmith reads to know what to build.
Never directly write or edit any project file. All project data must flow through MCP tools — manufacturing_annotate_tree, openrocket_component, etc. Direct file edits bypass schema validation and get silently overwritten on the next tool run. The sole exception in the overall pipeline is the CADSmith build123d Python scripts (cadsmith/source/*.py), which the cadsmith subagent writes — but that is not this agent's concern.
Never edit component_tree.json directly. Always use manufacturing_annotate_tree to annotate it and openrocket_component (action="read") to regenerate it. Direct edits are fragile — they get overwritten on the next regeneration and skip schema validation.
You do not run simulations. That's the openrocket agent's job. If your dimension changes affect stability, you send feedback to the openrocket agent to update the .ork file and re-verify.
Available MCP Tools
manufacturing_annotate_tree— Apply DFAM rules tocomponent_tree.json. Annotates each component with fate (print, fuse, purchase, skip), fusion directives, and AM-specific dimension adjustments. Acceptsfusion_overridesfor user-specified decisions.openrocket_component— Update component dimensions in the.orkfile when DFAM requires changes (e.g., wall thickness increase). Useaction="update"with the adjusted values.openrocket_component(action="read") — Regenerate the component tree after.orkchanges. Call withrocket_file_pathandproject_dirbut nocomponent_nameto get the full tree. The tree must be regenerated after any dimension changes so annotations reflect the current design.rocketsmith_setup— Check or install dependencies (action: check/install,project_dir: absolute path to the project)- Always pass
project_dir
- Always pass
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 · 165 lines · 349 tokens per session scan A 30ac1e75d9c6
manufacturing is an agent published in the GitHub repository ppak10/RocketSmith (21 stars, last pushed 4mo ago), licensed MIT. It adds 349 tokens to every session and 2,100 once invoked, about $0.0017 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
BIM/GIS Specialist
Integration specialist who bridges Building Information Modeling and Geographic Information Systems — Revit/IFC data conversion, indoor mapping, digital twin architecture, and facility management data models.
run neqsim mechanical design
Performs mechanical design and CAPEX calculations for process equipment and process systems — wall thickness, pipeline limit-state, free-span/VIV, pipe-soil interaction, global-buckling response, and corroded-pipeline metal-loss screening, material selection, weight estimation, CostEstimateResult reconciliation, and…
diagnose equipment root cause
Performs root cause analysis on process equipment using NeqSim's diagnostics framework — integrates multi-source reliability data (IOGP/SINTEF, CCPS, IEEE 493, Lees, OREDA), plant historian time-series, STID design conditions, and process simulation to produce ranked failure hypotheses with Bayesian confidence scoring.
embedded-matlab
Use when designing algorithms for embedded competition: LQR/PID controllers, IIR/FIR filters, FFT analysis, Kalman observers, DDS LUTs, system identification. Runs MATLAB via mcpmatlab tools, exports .h via . Skipped for SYSTEM-type problems with no algorithm TAGS.
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
rf-design-orchestrator
Orchestrates the RF/mmWave design flow (rfspec → topologymatching → sparameteranalysis → harmonicbalance → noiselinearity → loadpulloptimization → rfsignoff), signing off an LNA/mixer/VCO/PLL/PA block against the RF spec table across corners. Invoke to run the full RF flow or any individual stage, or to re-validate…