Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nebius/nebius-physical-ainpx agentmods add skills/nebius/nebius-physical-ai/byof-onboardWrote 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/byof-onboard)<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/byof-onboard"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/byof-onboard/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/byof-onboard"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/byof-onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 36 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 227 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00040 | $0.03181 |
| Opus 5 | $0.00020 | $0.01590 |
| Sonnet 5 | $0.00008 | $0.00636 |
| Haiku 4.5 | $0.00004 | $0.00318 |
Grade A, and why
byof-onboard 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 4d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BYOF Solution Onboard
Canonical procedure for bring-your-own-fork onboarding. The NPA agent onboard_solution
intent and run_byof_repo.py both follow this skill — do not duplicate long command blocks
in chat replies; point operators here.
When To Use
- Containerize a public GitHub/GitLab or private GitHub repo and push to an authorized registry
- Onboard a new workbench solution (toolRef + workflow + live smoke)
- LeIsaac validation (Isaac Lab base + datagen or RL)
- Generic Ubuntu BYOF (any OSS repo, no sim stack required)
For registry/catalog admission of an OSS Physical AI solution, also load
skills/workflows/oss-solution-registry-onboard/SKILL.md. BYOF proves the repo
can be packaged and run; registry admission additionally requires reading
upstream docs, listing that solution's native capabilities (use upstream
names), encoding each accepted claim as a solution-smoke with a named JSON
artifact, and collecting live Nebius validation evidence. See
docs/workbench/oss-solution-catalog.md.
Prerequisites
~/.npa/config.yaml— project alias, registry override,kubernetesblock (cluster_name,gpu_profile)- Exact-host registry credentials when the selected registry is private
- Private GitHub source: a fine-grained read-only token in an environment
variable, or an existing authenticated
ghlogin. Never put it in the URL. - Operator host: Docker,
nebiusCLI,sky(for GPU/container smokes) - SkyPilot must have Kubernetes enabled for the target context. The
solution-smokerunner runssky check kubernetesautomatically before submission; if debugging manually, run it with the resolved kubeconfig/context beforesky jobs launch. Container/solution smokes use directsky launch --downby default because the managed-jobs controller can retain a stale enabled-infra cache for newly synced Kubernetes contexts.
Project resolution: npa.workflows.byof.live.resolve_byof_project() — never hardcode VM paths.
Base Image Profiles
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.
- 4d ago Changed ecf407317805
- 9d ago First seen · 255 lines · 40 tokens per session scan A 474c3d49b8a9
byof-onboard is a skill published in the GitHub repository nebius/nebius-physical-ai (29 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 3,181 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-09-03.
Other skills, from other repositories
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger keywords - openshell…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.