How do I install the Codex Agent Setup skill?

Run npx skillmds@latest add b-open-io/codex-agent-setup-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codex Agent Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codex Agent Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codex Agent Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codex Agent Setup?

b-open-io (@b-open-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codex Agent Setup by b-open-io — Agent Skill

Name: Codex Agent Setup
Author: b-open-io

Codex Agent Setup

Explicit-only installer for the Sigma Auth Siggy Codex custom agent. Use ONLY when the user explicitly asks to install, update, check, uninstall, or set up the Sigma Auth or Siggy Codex agent, including "install Siggy in Codex", "update the Sigma Auth Codex agent", or "check sigma_auth_guide". Never auto-invoke for ordinary OAuth, authentication, Better Auth, BAP, wallet, session, passkey, or security requests.

b-open-io Updated Sep 22, 2026

File contents

Sigma Auth Codex Agent Setup

Install Siggy's generated Codex adapter as a regular file. Run this skill only after an explicit request to install, update, check, or uninstall Siggy.

Safety contract

Default to the current project's .codex/agents/ directory.
Use --user only when the user explicitly requests a user-wide install.
Never edit ~/.codex/config.toml or any global Codex configuration.
Never create plugin-cache symlinks or delete unrelated custom agents.
Run --check when the user asks what would change.

Commands

bash "${SKILL_DIR}/scripts/setup.sh" [--check|--uninstall|--force]
bash "${SKILL_DIR}/scripts/setup.sh" --user [--check|--uninstall|--force]
bash "${SKILL_DIR}/scripts/setup.sh" --target /custom/agents/directory

The installer manages only sigma-auth-guide.toml and records ownership in .sigma-auth-agents.json. An unmanaged collision is refused unless the user explicitly authorizes --force.

After a successful install or update, tell the user to start a new Codex session, then invoke Siggy using the runtime name sigma_auth_guide.

Maintainer generation

bash "${SKILL_DIR}/scripts/generate.sh"
bash "${SKILL_DIR}/scripts/generate.sh" --check

Frequently asked questions