Agent skill

Codex Profiles

by sickn33 in sickn33/agentic-awesome-skills

Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state.

MITAuto-check passed

Install Codex Profiles

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill codex-profiles -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills codex-profiles --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/codex-profiles .claude/skills/codex-profiles && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
codex-profiles
GitHub stars
47k
Used in
1 other repo
Token cost
~1.7k tokens
SKILL.md length
776 words
Files
1
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state.

  • Works in 4 steps: Confirm Scope and Installation → Create or Select a Profile → Run Codex CLI With a Profile → …
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 5 more sections
  • Calls codex, npm and brew

What it does

Codex Profiles is an agent skill from sickn33/agentic-awesome-skills. Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

Example prompts

  • “/codex-profiles”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Confirm Scope and Installation
  2. Create or Select a Profile
  3. Run Codex CLI With a Profile
  4. Use Desktop Profile Commands Carefully

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • codex
    • npm
    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Codex Profiles loads about 1.7k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 776 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 776 words, ~1,695 tokens.

Download SKILL.mdSave it as .claude/skills/codex-profiles/SKILL.md (or your agent's skills folder).
name
codex-profiles
description
Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEX_HOME profiles for separate accounts, projects, and local state.
category
productivity
risk
critical
source
community
source_repo
Ducksss/codex-profiles
source_type
community
date_added
2026-07-08
author
Ducksss
tags
codex, codex-cli, profiles, code-home, account-isolation, desktop
tools
codex
license
MIT

Codex Profiles

Overview

Use codex-profiles when a user wants separate Codex CLI or Codex Desktop contexts for work, personal, school, client, or project-specific activity. The tool wraps Codex's CODEX_HOME support so each profile has its own Codex home directory for auth, config, sessions, connectors, plugins, caches, logs, and local state.

This skill is for profile selection and operational safety around that boundary. It is not an official OpenAI project, and it does not provide full OS-level isolation.

When to Use This Skill

  • Use when the user wants to keep multiple Codex accounts or project contexts separate on one machine.
  • Use when a workflow needs a different CODEX_HOME without manually exporting environment variables.
  • Use when diagnosing which Codex profile is active or whether profiles are logged in.
  • Use when the user asks about Codex account switching without copying auth.json.
  • Use when launching Codex Desktop from a profile, only after confirming the user accepts app/process disruption.

How It Works

Step 1: Confirm Scope and Installation

First check whether the user wants CLI-only profile switching or Codex Desktop profile launching. Desktop operations can quit, launch, clone, or rebuild app instances, so get explicit approval before running them.

If the tool is already installed, inspect the live command surface:

bash
codex-profile --help
codex-profile doctor
codex-profile list
codex-profile status

If it is not installed, prefer package-manager installs the user can inspect and control:

bash
npm install -g codex-profile
brew install Ducksss/tap/codex-profile

Do not run remote install scripts automatically. If the user asks for a source install, clone the repository and inspect its install instructions first.

Step 2: Create or Select a Profile

Create a new isolated Codex home only when the user names the intended profile:

bash
codex-profile init work
codex-profile path work

Ask the user to log in once per profile when needed:

bash
codex-profile login work

Do not copy, parse, print, or migrate auth.json tokens between profiles.

Step 3: Run Codex CLI With a Profile

Use the CLI profile wrapper for ordinary agent work:

bash
codex-profile cli work
codex-profile cli work exec "run tests and summarize failures"

For one-off shell sessions, prefer the tool's environment or shell activation commands after checking --help:

bash
codex-profile env work
codex-profile shell-init --help
Step 4: Use Desktop Profile Commands Carefully

Codex Desktop launch flows can affect running app state. Before running them, state which profile, app mode, and workspace will be used, then wait for approval.

bash
codex-profile app work ~/Dev/project
codex-profile app work --instance ~/Dev/project

Use --instance only when the user wants side-by-side Desktop profiles and accepts the additional local app clone and separate Electron user-data boundary.

Examples

Example 1: Read-Only Profile Audit
bash
codex-profile list
codex-profile status
codex-profile doctor

Use this before changing profile state. It should not expose token contents.

Example 2: CLI Task in a Work Profile
bash
codex-profile cli work exec "inspect this repository and run its test suite"

Confirm the profile name is intentional before running long tasks.

Example 3: Manual CODEX_HOME Equivalent

If the wrapper is unavailable, explain the underlying boundary instead of improvising token movement:

bash
CODEX_HOME="$HOME/.codex-work" codex
CODEX_HOME="$HOME/.codex-work" codex exec "review this change"
Show full SKILL.md (348 more words)Show less

Best Practices

  • Keep profile names explicit and boring, such as work, personal, client-a, or school.
  • Use status, list, and doctor before destructive or Desktop actions.
  • Treat each profile as a separate local Codex home, not as a full sandbox.
  • Keep secrets inside the account/profile that owns them; do not copy auth files between profiles.
  • Prefer CLI profile commands for routine work and reserve Desktop app commands for user-approved context switches.
  • Verify behavior against the installed codex-profile --help, because command flags can change.

Limitations

  • codex-profiles is community-maintained and is not an official OpenAI tool.
  • It isolates Codex state through separate CODEX_HOME directories; it does not isolate the operating-system user, shell history, SSH keys, browser cookies, GitHub CLI auth, or unrelated application state.
  • Desktop profile launch behavior is macOS-focused and can change with Codex Desktop releases.
  • Existing Codex sessions may still contain project context from before a profile strategy was adopted.
  • The tool does not replace backups for important Codex state.

Security & Safety Notes

  • Never copy, print, parse, or migrate auth.json tokens as a shortcut.
  • Do not run Desktop launch, app clone, rebuild, remove, or profile deletion commands without explicit user approval.
  • Use codex-profile remove only after confirming the exact profile path and whether the user needs a backup.
  • Do not assume profile isolation protects credentials outside CODEX_HOME.
  • Avoid remote install scripts in automated agent runs; prefer inspectable package-manager or source-install steps.

Common Pitfalls

  • Problem: A user expects profile switching to isolate GitHub CLI, SSH, or browser state. Solution: Explain that codex-profiles isolates Codex home state only; check and switch other tools separately.

  • Problem: A Desktop command disrupts an active session. Solution: Ask before Desktop operations and prefer CLI commands when the user only needs isolated command-line work.

  • Problem: A profile exists but is logged out or missing connectors. Solution: Run codex-profile status and have the user log in or configure connectors inside that profile.

  • @environment-setup-guide - Use when installing or documenting local development tools.
  • @codex-maintenance - Use when maintaining local Codex Desktop, MCP, plugin, or cache surfaces.
  • @filesystem-context - Use when reasoning about local files, config paths, and workspace boundaries.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/codex-profiles of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Codex Profiles next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Codex Profiles compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codex Profiles this skillsickn33/agentic-awesome-skills47k1 repos~1.7kAutomated safety check: PassMIT
Profileccusage/ccusage19k—~430Automated safety check: PassCustom licence
Cpu ProfileClickHouse/ClickHouse50k—~1.9kAutomated safety check: NotesApache-2.0
Collectors Snmp Profilesnetdata/netdata81k—~3.1kAutomated safety check: PassGPL-3.0
Alloc ProfileClickHouse/ClickHouse50k—~4.3kAutomated safety check: PassApache-2.0
Generate Profilesgl-project/sglang37k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Profile

    ccusage/ccusage

    Profiles ccusage performance. An agent skill from ccusage/ccusage.

    19k GitHub stars~430 tokensUpdated today
    Auto-check passed
  • Cpu Profile

    ClickHouse/ClickHouse

    Profile a ClickHouse query using the sampling query profiler and system.tracelog.

    50k GitHub stars~1.9k tokensUpdated today
    DatabasesAuto-check: notes
  • Author or review Netdata SNMP polling profiles, ddsnmp parsing, topology/licensing/BGP rows and profile-format documentation.

    81k GitHub stars~3.1k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Alloc Profile

    ClickHouse/ClickHouse

    Analyze a jemalloc (or other) allocation profile in collapsed stack format.

    50k GitHub stars~4.3k tokensUpdated today
    DatabasesAuto-check passed
  • Generate Profile

    sgl-project/sglang

    Generate an e2e profiling trace of an SGLang server run. An agent skill from sgl-project/sglang.

    37k GitHub starsUsed in 2 repos~1.1k tokens
    Testing & QAAuto-check passed
  • Author or review Netdata SNMP trap profiles, metrics/charts rules, loader schema, snmp-trap-profile-gen, stock catalogue/compression and category/severity changes.

    81k GitHub stars~5.7k tokensUpdated today
    DevOps & CloudAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Codex Profiles

What does Codex Profiles do?

Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state. Codex Profiles is an agent skill from sickn33/agentic-awesome-skills. Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state.

How do I install Codex Profiles in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill codex-profiles -a claude-code`. Or copy the skill folder (skills/codex-profiles in sickn33/agentic-awesome-skills) into .claude/skills/codex-profiles in your project. Claude Code loads it when a task matches its description.

How do I install Codex Profiles in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill codex-profiles -a codex`. Or copy the skill folder (skills/codex-profiles in sickn33/agentic-awesome-skills) into .agents/skills/codex-profiles in your project. Codex loads it when a task matches its description.

Can I use Codex Profiles in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill codex-profiles -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codex-profiles, .gemini/skills/codex-profiles, .github/skills/codex-profiles and .opencode/skills/codex-profiles in your project.

What does Codex Profiles need to run?

Going by SKILL.md and its folder, Codex Profiles needs the command-line tools its instructions call (codex, npm and brew). Our summary lists: Node.js.

Does Codex Profiles access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Codex Profiles safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Codex Profiles use?

Codex Profiles is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codex Profiles use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Codex Profiles?

Skills that share tags, products or a category with Codex Profiles: Profile (ccusage/ccusage, 19k stars), Cpu Profile (ClickHouse/ClickHouse, 50k stars), Collectors Snmp Profiles (netdata/netdata, 81k stars) and Alloc Profile (ClickHouse/ClickHouse, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codex Profiles?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.