cursorrules

A set of instructions for working with a World Labs server that creates and manages generative 3D worlds. It covers creating worlds from text or images, checking generation progress, and managing saved worlds.

In plain words
What is it for?
Use it to create 3D worlds from prompts or images, check recent generations, browse or inspect saved worlds, and store generation details.
Why use it?
It gives an agent the required workflow for tracking asynchronous world generation and handling the world library without exposing API keys.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/sandraschi/worldlabs-mcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/sandraschi/worldlabs-mcp

Made for: Cursor.

Per session 175 This file is loaded in full into every session.
When invoked 175 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00175 $0.00175
Opus 5 $0.00088 $0.00088
Sonnet 5 $0.00035 $0.00035
Haiku 4.5 $0.00017 $0.00017

Measured 2d ago against content hash 122c86355531, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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.

.cursorrules · 20 lines

What it actually says

World Labs MCP - Cursor Rules

You are working with a World Labs MCP server that generates and manages generative 3D worlds, sparks, painting portals, and a world library.

  • Use generate_world_from_text / generate_world_from_image for new worlds
  • Poll get_operation for generation status (generations are async)
  • Use list_worlds / get_world for library queries
  • Never hardcode API keys; use env vars (WORLDLABS_*)

Session Context (World Labs MCP)

Before starting work:

  1. Check the world library: list_worlds(limit=10)
  2. Poll recent generations: get_operation(operation_id="<latest>")

At end of work:

  • Store generated world metadata in the library
  • Note generation failures with their operation IDs
Changes

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.

  1. 2d ago First seen · 20 lines · 175 tokens per session scan A 122c86355531

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sandraschi/worldlabs-mcp (22 stars, last pushed 4d ago), licensed MIT. It adds 175 tokens to every session, about $0.0009 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.