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 build-and-push-imagegit 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/build-and-push-image)<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/build-and-push-image"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/build-and-push-image/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/build-and-push-image"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/build-and-push-image.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01060 |
| Opus 5 | $0.00019 | $0.00530 |
| Sonnet 5 | $0.00008 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
build-and-push-image 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build And Push Image
Load and obey skills/atomic/secure-image-build/SKILL.md before every image
build, tag, push, copy, or promotion. That skill defines the mandatory order and
refusal conditions; this skill records NPA-specific build and GPU details.
Build Contract
Before building with npa/ as the Docker context, stage the top-level workflow
catalog into the ignored package data from the repository root:
npa/.venv/bin/python npa/src/npa/workflow_build.py --stage-catalog --package-root npa
Repeat after catalog edits. The generated main/ and testing/ copies under
npa/src/npa/workflows/ belong only to the build context; edit workflows/main/ and
workflows/testing/ as the source of truth.
- Build only a checked-in Dockerfile under
npa/docker/workbench/<tool>/. - Resolve the exact 40-character commit and use the one official namespace,
ghcr.io/nebius/nebius-physical-ai. A pre-release tag is exactlydev-<full-git-sha>on the normalnpa-<tool>package. - Require
redistribution: publicbefore any official push. Resolve the selected image's current classification fromnpa/docker/workbench/packaging-contract.yamland the restriction inventories innpa/src/npa/deploy/images.py; stop if they disagree. Build restricted images only into an operator-controlled registry; neither a private package nor a development tag changes licensing. Historical image classifications do not establish the eligibility of replacement bytes. The current catalog, for example, recordscosmos3-super-benchmarkas restricted; always re-read that classification before a build. - Run every pre-publication security, packaging, payload, provenance, SBOM, vulnerability, secret, non-root, base-pin, and bootstrap-contract gate before pushing the public development tag.
- After push, resolve the immutable digest, repeat exact-digest checks, and verify anonymous pullability. Use that digest for functional GPU validation.
- Promote only the real-GPU-validated digest to the supported release tag with
npa.deploy.publish_public; verify digest parity and anonymous pull afterward, then record the accepted release digest for anonymous read-only health checks.
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.
- 3d ago Changed · +16 lines 759a709be898
- 5d ago Changed d18c99c0f5d3
- 6d ago Changed · +2 lines d49de5d621d0
- 11d ago First seen · 72 lines · 39 tokens per session scan A 118df022e157
build-and-push-image is a skill published in the GitHub repository nebius/nebius-physical-ai (28 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 1,060 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-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.