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 skills/thrownlemon/claude-code-plugins/bambu-printernpx skills add ThrownLemon/claude-code-plugins --skill bambu-printergit clone --depth 1 https://github.com/ThrownLemon/claude-code-pluginsWhat 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.00049 | $0.01146 |
| Opus 5 | $0.00024 | $0.00573 |
| Sonnet 5 | $0.00010 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
bambu-printer 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 yesterday.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bambu printer skill — usage guide
You have access to the bambu CLI for controlling a Bambu Lab X1Plus 3D printer. Follow these rules every time the user mentions their printer.
Core principles
- Use the CLI, don't guess. Always run
bambucommands via the Bash tool to get real data. Never fabricate printer state, temperatures, or progress numbers. - Prefer
--jsonoutput. When a subcommand supports--json, use it — then parse and present the result in a human-readable format. - Recommend slash commands. If the user's request maps cleanly to a plugin command, suggest the slash form:
/bambu:status— quick status check/bambu:print— send & start a print/bambu:control— pause / resume / cancel/bambu:calibrate— bed or vibration calibration
- Quote all file paths and arguments. Filenames with spaces or special characters must be properly quoted.
Command quick reference
| Intent | Command |
|---|---|
| Current state | bambu status --json |
| Printer info | bambu info --json |
| Send file | bambu gcode send "<file>" |
| List files on printer | bambu gcode list |
| Start remote print | bambu gcode start "<file>" |
| Pause / Resume / Cancel | bambu gcode pause / resume / cancel |
| Print history | bambu history --json |
| Calibrate | bambu calibrate bed / vibration / all |
| Filament | bambu filament list / add <name> / remove <name> |
| Camera analysis | bambu xcam first-layer / spaghetti |
| Diagnostics | bambu doctor --json |
| Automation scripts | bambu script <name> |
| SSH (X1Plus) | bambu ssh "<command>" |
| Config | bambu config set <k> <v> / get <k> (never list — prints secrets) |
Destructive-operation policy
Before executing any of the following, stop and ask the user for explicit confirmation:
bambu gcode start— starts a physical print (consumes filament & machine time)bambu gcode cancel— aborts the current printbambu calibrate *— takes the printer offline for several minutesbambu ssh *— runs arbitrary commands on the printer OSbambu filament remove— removes a filament profile
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.
- yesterday First seen · 115 lines · 49 tokens per session scan A 6023a5b7554a
bambu-printer is a skill published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,146 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…