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 skills add nebius/nebius-physical-ai --skill marblegit clone --depth 1 https://github.com/nebius/nebius-physical-aiWrote 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/skills/nebius/nebius-physical-ai/marble)<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/marble"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/marble/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/skills/nebius/nebius-physical-ai/marble"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/marble.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.00029 | $0.01481 |
| Opus 5.5 | $0.00012 | $0.00592 |
| Sonnet 5.5 | $0.00006 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
marble 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 11d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marble
For generated-site Go1 inspection, use one workflow:
workflows/testing/marble-go1-inspection.yaml with exactly one native
--preset warehouse|shipyard|home|factory|utility selection. Omission defaults
to warehouse. Each submission runs one hosted generation using WLT_API_KEY,
one RTX PRO 6000 collection and one continuous 25 FPS standalone HTML report.
It never fans out across situations. The guide is
docs/workbench/guides/marble-robot-presets.md; for a custom world, omit
--preset and override world_prompt and workflow_preset on the same YAML.
Use the native write_quadruped_gallery to combine completed reports into an
offline situation selector retaining every original video and trajectory row.
All five parameterizations have prior native GPU evidence from the retired
combined workflow; distinguish that evidence from new-entrypoint submissions.
These are Go1 presets, not ANYmal or Spot. Do not advertise thermal inspection,
defect detection, household manipulation or new RL training.
For detailed quadruped collection, use
workflows/testing/marble-warehouse-quadruped.yaml and
docs/workbench/guides/marble-warehouse-quadruped.md. Reuse an existing generated
warehouse: no new World API request is needed. The runtime verifies pinned
official Unitree Go1 meshes and a Google MuJoCo Playground ONNX policy. PyBullet
torque dynamics and ONNX inference execute on CPU; gsplat RGB, Warp depth, and
Cycles CUDA articulated rendering use one RTX PRO 6000. OpenImageDenoise runs
on CPU; CPU path tracing is rejected. This is pretrained-policy collection, not new RL training or a
physical robot connection. Preserve upstream licenses, actual link poses,
per-foot contact forces, raw depth, and per-frame renderer evidence in the
standalone HTML and collection bundle. Verify the completed run and browser
playback before claiming live acceptance.
For GPU learning beyond rendering, use workflows/testing/marble-navigation-rl.yaml
and docs/workbench/guides/marble-navigation-rl.md. The
workbench.marble.navigation_prepare adapter preserves a generated world's
collision triangles, measures supported cases with disjoint goal locations,
and seals inputs for the existing native ANYmal/Isaac/RSL-RL trainer. Training
and evaluation use standard Workbench/SkyPilot stages and immutable S3 handoffs.
Require an operator-qualified immutable Isaac image; do not default to the
quarantined public release. This adapter's CPU preparation is verified against
the real warehouse, but native GPU PPO and held-out evaluation remain unverified.
The earlier sensor collection cannot establish navigation learning acceptance.
WLT_API_KEY is needed for upstream generation, not for reusing its world bundle.
For embodied warehouse collection, use
workflows/testing/marble-warehouse-rover.yaml and
docs/workbench/guides/marble-warehouse-rover.md. It requires real World API
generation and aligned mesh/splat transforms. workbench.marble.rover_collect
drives a four-wheel rover through PyBullet CPU rigid-body dynamics, then renders
RGB with gsplat CUDA and raycasts depth with Warp CUDA on one Nebius GPU. It
saves actions, joints, contacts, poses, raw depth, and a standalone HTML replay.
The observer uses a CPU-rendered rover at recorded poses and CUDA mesh depth
occlusion. Do not describe this as physical Spot collection or RL training.
Run native runtime submission from a Linux operator and preserve its isolated
SkyPilot identity for resume and cleanup.
For a straightforward user walkthrough, use
docs/workbench/guides/marble-to-nebius.md: World Labs generates the scene,
the CPU acquisition stage downloads files to S3, and a Nebius GPU worker loads
those files for rendering or scanning. The report replays completed outputs.
For manufacturing, use workflows/testing/marble-manufacturing-pallet-detection.yaml.
It requires WLT_API_KEY and a real pallet dataset manifest, fails before
generation on missing auth or invalid/overlapping data, and never substitutes
the sample world. Native submit automatically resolves and forwards this token
from the environment or private NPA credentials. See
docs/workbench/marble-manufacturing.md for the fully headless command.
The experiment renders factory backgrounds on CUDA, composites training-only
RGBA pallet cutouts, and invokes the existing Faster R-CNN trainer/evaluator
on CUDA. Both arms receive matched optimizer-update counts and use the same
held-out real evaluation partition. Report negative AP changes honestly.
This is a 2D background-augmentation experiment, not a physics simulation or
production accuracy claim. New manufacturing execution is unverified until a
funded API credential and the operator's real dataset are supplied.
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.
- 11d ago First seen · 111 lines · 29 tokens per session scan A b29c881f6b56
marble is a skill published in the GitHub repository nebius/nebius-physical-ai (50 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 1,481 once invoked, about $0.0001 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-10-11.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…