What is submit-workflow?

A procedure for submitting and checking workflow YAML files used with SkyPilot, a system for running jobs across computing resources. It covers the project’s command-line, software-library, and YAML submission paths.

Validating workflow specifications, preparing NPA workflow YAML, submitting jobs, locating the configured SkyPilot executable, and troubleshooting runner paths.

It reduces mistakes from using the wrong SkyPilot command, workflow format, or cleanup behavior. It also keeps shared controllers from being removed accidentally.

submit-workflow — Skill for Claude Code and Codex by nebius

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.

Any agent

npx skills add nebius/nebius-physical-ai --skill submit-workflow

Clone the repo

git clone --depth 1 https://github.com/nebius/nebius-physical-ai

Made for: Claude Code, Codex.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/submit-workflow/github.svg)](https://agentmods.dev/skills/nebius/nebius-physical-ai/submit-workflow)

Your own site

<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/submit-workflow"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/submit-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/submit-workflow"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/submit-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,847 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, 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 62
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.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.03847
Opus 5.5	$0.00010	$0.01539
Sonnet 5.5	$0.00005	$0.00769
Haiku 4.5	$0.00002	$0.00385

Measured 12d ago against content hash 742ed723c059, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

submit-workflow 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 12d 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.

skills/atomic/submit-workflow/SKILL.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Submit Workflow

When To Use

Use this skill for workflow launch, YAML validation, runner scripts, and SkyPilot submission behavior.

Procedure

Read skills/tools/skypilot-workflows/SKILL.md for SkyPilot version and cleanup constraints.
Prefer npa.workflow/v0.0.1 specs under workflows/. Parse / validate-spec locally before launch.
Use NPA_SKYPILOT_BIN or npa skypilot status --bin-path; do not assume sky from PATH.
Submit through npa workbench workflow submit (accepts npa.workflow specs and legacy SkyPilot YAML) or the shared workflow submission helper.
Keep cleanup best-effort and avoid tearing down a shared controller unless the operator explicitly requests it.

Three-Tier Contract

CLI: npa workbench workflow --help and tool-specific workflow commands.
SDK: use shared workflow submission helpers rather than shelling out from application logic.
YAML: author shipped workflows as npa.workflow/v0.0.1 specs under workflows/testing/; promoted principal pipelines live in workflows/main/ and partner integrations in workflows/partners/<partner>/. See the catalog for their runbooks and validation scope. npa workbench workflow submit accepts those specs (plans, renders, then launches SkyPilot) and still accepts raw SkyPilot YAML supplied by an operator or by guarded single-task example directories.

Live submit prerequisites (real cluster)

A real npa workbench workflow submit (not --plan-only) needs, on top of a successful npa skypilot verify --cluster <exact-context>:

Secrets via --secret-env (never in the YAML): NEBIUS_TOKEN_FACTORY_KEY for Token Factory stages, AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY for S3, HF_TOKEN / NGC_API_KEY for gated model pulls. Submit resolves each requested name from the explicit process environment first, then the selected project's configured NPA credentials; it fails locally if the value is unavailable.
NPA source for steps that need it. Submit automatically stages missing or outdated saved source from the local editable checkout under a content-addressed S3 prefix and reuses verified matching source. An exported NPA_SRC_S3_URI or NPA_E2E_NPA_SRC_S3_URI is an explicit selection and is retained. For a new run after upgrading, clear an old export or use --stage-src to force restaging; leave --no-stage-src off for the automatic path. Updating NPA does not require syncing an unchanged input dataset or the whole bucket. Specs with config.source_overlay: true also apply the submitted NPA code inside pinned workbench images.
Dynamic decisions. --assume-decision promote_checkpoint previews an accepted path in plan-spec, preflight-images, or submit --plan-only. For execution, specs declaring metadata.executionMode: runtime, including PAIDF Cosmos3, select the runtime automatically and reject assumed decisions. Keep --runtime and omit --assume-decision when executing that workflow; actual evaluator decisions control its refinement and terminal routing. See the PAIDF Cosmos3 upgrade guidance.
--var key=value to override config (e.g. --var bucket=<real-bucket>; the reference specs default to bucket: example-bucket).

Read the full file on GitHub · 259 lines

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.

12d ago Changed · +2 lines 742ed723c059
19d ago Changed · +43 lines d09d4b3861aa
1mo ago Changed · +9 lines 019b3f02a71d
1mo ago Changed · +1 lines c6f67c5b17af
1mo ago First seen · 204 lines · 24 tokens per session scan A 8e0d13d8b5ab

Subscribe to this mod's changes

submit-workflow is a skill published in the GitHub repository nebius/nebius-physical-ai (50 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 3,847 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-08-30.

Cloud DevOps and cloud

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…

google/skills · 171 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…

google/skills · 85 tokens

cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…

Jeffallan/claude-skills · 71 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens