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.
git clone --depth 1 https://github.com/ppak10/RocketSmithWrote 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.
[](https://agentmods.dev/agents/ppak10/rocketsmith/manufacturing)<a href="https://agentmods.dev/agents/ppak10/rocketsmith/manufacturing"><img src="https://agentmods.dev/badge/agents/ppak10/rocketsmith/manufacturing/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.
<a href="https://agentmods.dev/agents/ppak10/rocketsmith/manufacturing"><img src="https://agentmods.dev/badge/agents/ppak10/rocketsmith/manufacturing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00349 | $0.02100 |
| Opus 5.5 | $0.00140 | $0.00840 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed MIT. It adds 349 tokens to every session and 2,100 once invoked, about $0.0014 per session on Opus 5.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
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
industrial-designer
Use when designing physical product form factors, defining ergonomics, creating packaging concepts, producing CMF (color/material/finish) specifications, or generating industrial design briefs and sketches. Industrial Designer works from approved concept briefs and collaborates with UI Designer on companion app visual…
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.
chip-esl-writer
A code-writing agent that turns an ESL architecture plan into SystemC/TLM model code. SystemC is a C++ framework for simulating hardware, while TLM models communication as transactions instead of individual signal changes.
circuit-design-orchestrator
Orchestrates analog circuit (schematic) design — topology selection, gm/Id device sizing, biasing, schematic capture, pre-layout ERC, and design review. Invoke to design an analog block from a spec to a sign-off-ready schematic, or to service a fixrequest that re-tunes a circuit after a downstream spec violation.
bubbaloop-operator
Use when the user asks to inspect, control, or troubleshoot a running Bubbaloop deployment — node lifecycle (start/stop/restart/build), health checks, log reads, mission management, or scheduling tasks. Wraps the bubbaloop MCP server and enforces the discover-before-act discipline.