agent-nebius-auth-setup

Bootstrap and repair persistent Codex Agent service-account authentication for Nebius projects.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill agent-nebius-auth-setup-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-nebius-auth-setup
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/agent-nebius-auth-setup
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill agent-nebius-auth-setup-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Setting up persistent, least-privilege Nebius authentication for an AI coding agent requires manual IAM work: creating a service account, granting the right project and tenant roles, generating authorized-key credentials, and binding a CLI profile. This Skill performs that bounded convergence explicitly and safely, with strict fail-closed behavior. ## Core Features & Use Cases - Bounded IAM convergence: Creates or reuses one deterministic tenant-parented group with exactly project admin and tenant viewer permits plus one codex-agent-sa membership, rejecting extra or duplicate permits and members. - Credential and profile lifecycle: Generates identity-checked authorized-key credentials, atomically replaces stale credentials at most once, and rebuilds the project-bound CLI profile without printing or persisting human tokens. - Read-only verification and repair leases: verify checks credential safety, identity binding, project access, and tenant quota listing without mutation; an explicitly requested repair lease authorizes only mode-0600 credential correction and profile rebuild. - Use Case: Before letting a Codex agent run Nebius CLI commands against project-abc123, explicitly invoke the skill to converge the service account, group, credential, and profile in one pass, then verify runtime auth read-only. ## Quick Start Ask the agent to explicitly run agent-nebius-auth-setup with your project ID to converge the service account, IAM group, credential, and CLI profile for that Nebius project.

Frequently Asked Questions about agent-nebius-auth-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Nebius service-account authentication for a Codex agent?

Explicitly invoke the skill with your project ID, which runs `bash scripts/agent-nebius-auth-setup.sh ensure --project-id <id>`. Direct invocation authorizes one bounded convergence covering the service account, IAM group, credential, and CLI profile without a second confirmation.

What IAM permissions does the Nebius agent setup grant?

It grants exactly two permits on one deterministic tenant-parented group: `admin` on the selected project and `viewer` on its parent tenant, with the fixed `codex-agent-sa` service account as the sole member. Extra or duplicate permits and members cause a fail-closed stop before any mutation.

Can I preview Nebius auth setup changes before applying them?

Yes, run ensure with `--dry-run` to see the resolved target, planned mutations, and any conditional credential replacement without modifying local files or cloud IAM. A dry-run is read-only and does not authorize a later run; the later explicit invocation is the authority.

What happens if the existing Nebius credential stops working?

If the canonical credential fails with a classified authentication error, ensure backs it up at mode 0600 and replaces it at most once, then rebuilds the profile. Transient, unclassified, or profile-write failures stop without replacement, and no second key is generated.

Does the setup skill install runtime auth hooks automatically?

No, hook installation is a separate explicit action using `./install-skills.sh --install-hooks agent-nebius-auth-setup/assets/hooks --register-hooks`. The skill never mutates hooks, IAM, credentials, or profiles unless it was explicitly invoked.

How does the skill resolve which Nebius project to configure?

It resolves exactly one project ID in priority order: explicit ID in the current turn, task-labeled state, task-tied workspace config, then the config-owned default profile's configured `parent-id`. Conflicting authoritative sources or only stale memory cause it to ask the user instead of guessing.