Publish Registry

DevOps & Security

publish-registry

Publish Registry is an Agent Skill for devops & security published in the rivet-dev/agentos repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Publish @agentos-software/* registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/rivet-dev/agentos/blob/HEAD/.claude/skills/publish-registry/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/publish-registry, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Publish AgentOS Registry Packages

Registry packages live in agentos/registry and publish as @agentos-software/*. They version independently per package.

Procedure

Build native command artifacts and package tarballs:

just registry-native
just registry-build [pkg]
just registry-status --remote

Bump the package's own package.json version and commit it.
Publish from AgentOS:

just registry-publish <pkg>         # dist-tag dev
just registry-publish <pkg> latest  # deliberate latest release
just registry-publish-all [tag]

Rules

Do not publish registry packages from secure-exec.
Do not move latest unless the user explicitly asks for a release.
Prefer AgentOS workspace builds while iterating; published pins are for consumers and release validation.