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/lesleslie/spline-mcpWrote 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/commands/lesleslie/spline-mcp/spline-generate)<a href="https://agentmods.dev/commands/lesleslie/spline-mcp/spline-generate"><img src="https://agentmods.dev/badge/commands/lesleslie/spline-mcp/spline-generate/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/commands/lesleslie/spline-mcp/spline-generate"><img src="https://agentmods.dev/badge/commands/lesleslie/spline-mcp/spline-generate.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.00024 | $0.00612 |
| Opus 5 | $0.00012 | $0.00306 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
spline-generate 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 8d 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.
What it actually says
/spline-generate
Generate a complete Spline 3D scene integration (component code + variable bindings + event handlers + WebSocket hookup) from a Spline scene URL or scene ID.
Usage
/spline-generate <scene-url-or-id> [--framework react|nextjs|vanilla] [--typescript] [--lazy-load] [--no-semicolons]
Arguments:
<scene-url-or-id>: full Spline export URL (https://prod.spline.design/<id>/scene.splinecode) or a bare scene ID. The scene must have been previously downloaded bymcp__spline__download_sceneand live in the cache.--framework react|nextjs|vanilla: optional target framework. Defaults toreact.--typescript: optional flag. Emit TypeScript instead of plain JavaScript. Defaults to on for React/Next.js.--lazy-load: optional flag. Wrap the scene inReact.lazy+<Suspense>. Defaults to on for React/Next.js.--no-semicolons: optional flag. Emit code without trailing semicolons.
Workflow
- Call
mcp__spline__parse_scene_urlon the input to extract the canonical scene ID (or accept it as-is if a bare ID was supplied). - Call
mcp__spline__build_export_urlto derive the export URL the server will use to fetch the cached scene. - Call
mcp__spline__validate_sceneon the resolved URL to confirm the.splinecodepayload is well-formed before generation. - Call
mcp__spline__generate_full_integrationwith the resolved URL and the chosen framework/options. This returns the full component, variable bindings, event handlers, and WebSocket hookup in one response. - If the user only wants a single snippet (e.g. just the runtime initialization block), call
mcp__spline__generate_snippetinstead ofgenerate_full_integration. - Report the generated code and any next-step hints (e.g. which package to install, how to wire the WebSocket channel).
Example
/spline-generate https://prod.spline.design/6Wq1Q7YGyM-iab9i/scene.splinecode --framework react
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.
- 8d ago First seen · 35 lines · 24 tokens per session scan A 4b642d1ce01b
spline-generate is a command published in the GitHub repository lesleslie/spline-mcp (4 stars, last pushed 7d ago), licensed BSD-3-Clause. It adds 24 tokens to every session and 612 once invoked, about $0.0001 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 commands, from other repositories
seed-create-component
A command for creating a new SEED Design component, including its source specification, recipes, React implementation, documentation, examples, and optional headless layer.
sddesign
Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.
craft
One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
spec-screenshot
Analyze website screenshots and generate detailed implementation specs.