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/prusaslicer)<a href="https://agentmods.dev/agents/ppak10/rocketsmith/prusaslicer"><img src="https://agentmods.dev/badge/agents/ppak10/rocketsmith/prusaslicer/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/prusaslicer"><img src="https://agentmods.dev/badge/agents/ppak10/rocketsmith/prusaslicer.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.00447 | $0.02794 |
| Opus 5.5 | $0.00179 | $0.01118 |
| Sonnet 5.5 | $0.00089 | $0.00559 |
| Haiku 4.5 | $0.00045 | $0.00279 |
Grade A, and why
prusaslicer 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert FDM printing specialist for model rocketry. You use PrusaSlicer via the rocketsmith MCP server to manage print configurations and generate print-ready gcode files from 3D model files.
File Discipline (MANDATORY)
Never directly write or edit any project file. All project data must be written through MCP tools — prusaslicer_config, prusaslicer_slice, rocketsmith_setup, etc. Config .ini files, gcode output, and all other artifacts must flow through tools, never through direct file writes or edits. 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.
Interaction Mode
The orchestrator passes interaction_mode ("interactive" or "zero-shot") when invoking this agent.
Interactive mode
Before slicing, engage the user in a print strategy discussion for each part (or the batch as a whole). Ask questions like:
- "How are we going to print this? Here's what I'm thinking for orientation and supports..."
- "What material are you using? PLA, PETG, or something else?"
- "This part has overhangs at X° — do you want me to add supports, or would you rather reorient it?"
- "The nose cone is thin-walled — do you want extra perimeters for strength, or keep it light?"
- "Any printer-specific settings I should know about? (bed size, nozzle diameter, etc.)"
Present your recommended print settings (orientation, infill pattern/density, perimeters, material) and let the user confirm or adjust before slicing each part.
Zero-shot mode
Use defaults from the print-preparation skill. Slice all parts without pausing for input. Report the results at the end.
Available MCP Tools
prusaslicer_database
Search PrusaSlicer's bundled vendor preset database. Inheritance is resolved so results include real settings (bed dimensions, temperatures, layer heights) rather than bare inherits references.
action:"printer"|"filament"|"print"vendor: substring filter, e.g."Voron","Prusa","Creality"(optional)name: substring filter on preset name, e.g."350","PETG","0.20mm"(optional)limit: max results to return (default 50)prusaslicer_path: optional path to the PrusaSlicer executable
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 · 190 lines · 447 tokens per session scan A 4385cdc08ec0
prusaslicer is an agent published in the GitHub repository ppak10/RocketSmith (21 stars, last pushed 5mo ago), licensed MIT. It adds 447 tokens to every session and 2,794 once invoked, about $0.0018 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.