New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Codexless Browser Repair

by liyana31811 in liyana31811/Codexless

Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working.

Apache-2.0Auto-check passedAgent Workflows

Install Codexless Browser Repair

skills CLI
$ npx skills add liyana31811/Codexless --skill codexless-browser-repair -a claude-code

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

GitHub CLI
$ gh skill install liyana31811/Codexless codexless-browser-repair --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/liyana31811/Codexless.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/codexless-browser-repair .claude/skills/codexless-browser-repair && 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
codexless-browser-repair
GitHub stars
118
Token cost
~2.2k tokens
SKILL.md length
1,103 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working.

  • Works in 7 steps: Identify the target before touching it → Run model-free compatibility evidence… → Classify before calling Codex → …
  • Current-version Codexless Browser compatibility drift
  • SKILL.md covers Core contract, 1. Identify the target before…, 2. Run model-free… and 3. Classify before calling Codex, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Codexless Browser Repair is an agent skill from liyana31811/Codexless. Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working. Use for current-version Codexless Browser compatibility drift, not ordinary website bugs, general Browser operation, Codexless install/update work, or long-term compatibility architecture.

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

It sits in Agent Workflows. It works with Model Context Protocol and OpenAI. The repository describes itself as: Let ChatGPT use Codex's local toolbox, then call Codex only when needed. The licence is Apache-2.0.

When your agent uses it

  • Current-version Codexless Browser compatibility drift
  • Not ordinary website bugs
  • General Browser operation
  • Codexless install/update work

Example prompts

  • “/codexless-browser-repair”

Workflow steps

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

  1. Identify the target before touching it
  2. Run model-free compatibility evidence first
  3. Classify before calling Codex
  4. Escalate to Codex only for class B
  5. Temporary installed-release patch protocol
  6. Validate without manufacturing risk
  7. Report and stop

What it can do on your machine

Read from SKILL.md and the folder at commit e92b7af. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Codexless Browser Repair loads about 2.2k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 1,103 words of instructions outside code blocks.

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

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 liyana31811/Codexless at commit e92b7af, republished under its Apache-2.0 licence (© liyana31811). 1,103 words, ~2,187 tokens.

Download SKILL.mdSave it as .claude/skills/codexless-browser-repair/SKILL.md (or your agent's skills folder).
name
codexless-browser-repair
description
Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working. Use for current-version Codexless Browser compatibility drift, not ordinary website bugs, general Browser operation, Codexless install/update work, or long-term compatibility architecture.

Codexless Browser Repair

Use this Skill only for a current-machine Codexless Browser compatibility failure after upstream Codex / Chrome Skill / Browser runtime changed. The normal product path is automatic compatibility through the Codexless scanner, fingerprint, and known adapters. This Skill is the last-resort self-rescue path for an unknown Browser drift.

Core contract

  • Keep the user in the Chat entry point. Chat diagnoses and coordinates; Codex is called only when an unknown code-level Browser drift genuinely needs a repair worker.
  • Start model-free. A Codex version/build change by itself is not a repair reason.
  • Do not turn this Skill into a permanent compatibility framework, updater, daemon, or authority layer.
  • Do not modify upstream Codex bundles, Chrome extension files, .codex/plugins cache, or private Browser service internals.
  • Never widen Codex trust, permission profile, roots, network authority, or approval policy to make a repair pass.
  • Never use private turnEnded, forged rollout JSONL, fake Codex turn completion, or another unproven private cleanup path to manufacture Browser handback/release.
  • Ordinary website failures, login problems, selector/page-layout bugs, and normal Browser operation are not this Skill.

1. Identify the target before touching it

Determine whether the task targets:

  • the Codexless household/source checkout, where a formal source fix is appropriate; or
  • an installed Codexless release, where only a temporary local Browser repair is allowed.

Do not guess an install root from memory. Resolve it from the actual Codexless launcher/doctor/runtime context available on the machine. Do not treat the upstream Codex/Chrome plugin directory as the Codexless repair target.

2. Run model-free compatibility evidence first

From a Codexless tree that contains the compatibility reporter, run it in a host-state context that can read the current user Codex config, Skills, and plugin cache:

text
npm run compatibility:report

Do not treat a sandboxed collector as upstream evidence. If the report says collectionEnvironment.status=INCOMPLETE, compatibilityDecisionUsable=false, or fingerprint.relevantCapabilityHash=null, re-run it from the correct host-state lane before classifying drift. In particular, config_overrides_unreadable or a missing current Chrome Skill from an incomplete collection environment is not by itself evidence that upstream compatibility broke.

Also use the current model-free Browser status/catalog surfaces when available. If Browser status explicitly reports BROWSER_RUNTIME_COMPAT_CHANGED_RESTART_REQUIRED, restart/rebind the Codexless-owned runtime and retry before escalating. That is normal compatibility recovery, not a code repair. A Codex Desktop restart is a last-resort user recovery only if a fresh App Server still cannot discover the current Skill/Browser state after Codexless has refreshed its own runtime.

Collect only evidence relevant to compatibility, such as:

  • resolved Codex executable/version and platform/arch provenance;
  • Chrome Skill / Browser bundle build pairing;
  • node_repl server, js tool, and normalized input schema shape;
  • Browser client lifecycle members and the existing normalized lifecycle classification;
  • relevant capability fingerprint/hash and structured warnings/unavailable reasons.

Do not inspect or mutate a real user tab merely to diagnose an upstream compatibility drift.

3. Classify before calling Codex

A. Compatible or already known

If relevant capabilities are unchanged or an existing adapter already handles the observed shape, do not call Codex. Use the ordinary Codexless path or report the actual non-compatibility problem.

B. Unknown relevant Browser drift, capability may still exist

Only this class proceeds to a formal Codex code-repair task.

C. Capability missing or safety semantics unproven

Stop and fail visibly. Examples include no public release/unclaim/finalize path, a required Browser capability being absent, or approval/ownership/replay semantics that cannot be proven equivalent. Do not replace an upstream capability gap with a private workaround.

4. Escalate to Codex only for class B

Before local reverse engineering, inspect the current official openai/codex source/protocol when it can explain the observed shape: App Server protocol/schema, relevant Browser/feature configuration, and the source or release diff around the resolved Codex build. Treat upstream source as an explanation aid, not runtime truth; confirm it against the user's actual fingerprint. Only inspect local Desktop/Browser bundle internals when the public source/protocol does not explain the seam.

When Codex is needed, keep the task narrow. Give it:

  • the compatibility report/evidence;
  • the exact Codexless target root;
  • the current Codex/Chrome Skill/Browser bundle evidence;
  • any relevant official upstream source/protocol evidence already found;
  • the specific Browser compatibility adapter/source and directly relevant tests or verifier paths;
  • this Skill as the repair contract.

The Codex task is to find the smallest current-version compatibility patch. Typical repairable drift includes path/member renames, schema-shape changes, or a changed Browser facade where equivalent upstream capability still exists.

Do not ask Codex to redesign Codexless, update unrelated features, alter authority, or solve a missing upstream capability.

Show full SKILL.md (379 more words)Show less

5. Temporary installed-release patch protocol

For an installed release, a code patch is allowed only when diagnosis proves class B and the user has asked to repair Browser. Before changing files:

  1. Record the installed Codexless release identity and current relevant upstream fingerprint.
  2. Select only the Codexless Browser-compatibility files required by the repair.
  3. Record each target file's relative path and pre-repair SHA-256.
  4. Create a recoverable backup outside the release tree under a user-local Codexless repair state directory.

Recommended receipt location:

text
~/.config/codexless/browser-repairs/<repair-id>/
  repair.json
  backup/...

The receipt may contain base release identity, relevant fingerprint/hash, changed relative paths, pre/post hashes, validation results, and repair status. Do not store tab URLs/titles, account identity, prompts/transcripts, tokens/quota, credentials, or secrets.

After the patch:

  • record post-repair hashes;
  • do not change or fake the package version;
  • state clearly that this installation has a temporary local Browser repair;
  • keep the backup until an official Codexless update/reinstall supersedes the repair.

A later official Codexless install is authoritative and may replace the temporary repair. Never replay a stale repair over a newer official install.

6. Validate without manufacturing risk

For a source checkout, run the current relevant compatibility/Browser regressions. At minimum use the compatibility reporter and the Browser-related targeted tests supplied by that checkout.

For an installed release that does not ship test fixtures, validate with the packaged model-free compatibility reporter and current read-only Browser status first. Only use a disposable/low-risk Browser smoke if static/model-free evidence is insufficient, and follow the current Browser confirmation policy. Do not use a real user tab as a disposable fixture.

A repair is not accepted merely because code loads. Verify that:

  • the previously unknown relevant shape is now recognized without lying about unsupported capability;
  • node_repl/js and bundle pairing remain fail-closed where required;
  • existing-tab release/handback is never reported proven unless the current public upstream shape actually proves it;
  • no unrelated authority or product surface changed.

7. Report and stop

Return a compact repair receipt to Chat/user:

  • what drift was found;
  • whether Codex was needed;
  • files changed and backup/rollback location;
  • validation performed and results;
  • what remains unverified;
  • whether the result is a temporary local repair or a formal source fix;
  • what upstream fact would make the repair unnecessary.

Then stop. Do not continue into long-term adapter/state-machine design, release publishing, push, or unrelated cleanup unless separately authorized.

© liyana31811, Apache-2.0. 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/codexless-browser-repair of liyana31811/Codexless.

Open the folder on GitHubat commit e92b7af

Compare with similar skills

Codexless Browser Repair 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.

Codexless Browser Repair compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codexless Browser Repair this skillliyana31811/Codexless118—~2.2kAutomated safety check: PassApache-2.0
Codex with ChatGPT Planning LoopXiaoDuoYa/codex-with-chatgpt7.2k—~11kAutomated safety check: NotesMIT
Cao MCP Appsawslabs/cli-agent-orchestrator1.4k—~1.9kAutomated safety check: PassApache-2.0
Chatgpt AppsHaohao-end/openagent7911 repos~4.9kAutomated safety check: PassApache-2.0
Chatgpt App Builderalpic-ai/skybridge2.2k—~1kAutomated safety check: PassMIT
Agent QA Authoringvostride/agent-qa904—~569Automated safety check: PassCustom licence

Similar skills

  • Codex with ChatGPT Planning Loop

    XiaoDuoYa/codex-with-chatgpt

    Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.

    7.2k GitHub stars~11k tokensUpdated 10 days ago
    Agent WorkflowsAuto-check: notes

  • Cao MCP Apps

    awslabs/cli-agent-orchestrator

    Official

    Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman).

    1.4k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Chatgpt Apps

    Haohao-end/openagent

    Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI.

    791 GitHub starsUsed in 1 repo~4.9k tokens
    Agent WorkflowsAuto-check passed

  • Chatgpt App Builder

    alpic-ai/skybridge

    Guide developers through creating and updating ChatGPT plugins.

    2.2k GitHub stars~1k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Agent QA Authoring

    vostride/agent-qa

    A skill your agent uses when creating, editing, validating, or running agent-qa tests, suites, or hooks.

    904 GitHub stars~569 tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

  • MCP Apps Builder

    awslabs/cli-agent-orchestrator

    Official

    Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.

    1.4k GitHub stars~1.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from liyana31811/Codexless

  • Codexless Release Supervisor

    liyana31811/Codexless

    Prepare, validate, and publish Codexless preview/hotfix releases from the canonical household source, including acceptance anti-omission gates, candidate provenance/parity, manifest/build identity…

    118 GitHub stars~2.4k tokensUpdated 12 days ago
    Auto-check passed

Works with

Categories

Questions about Codexless Browser Repair

What does Codexless Browser Repair do?

Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working. Codexless Browser Repair is an agent skill from liyana31811/Codexless. Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working.

When should I use Codexless Browser Repair?

Codexless Browser Repair fits situations like: current-version Codexless Browser compatibility drift; not ordinary website bugs; general Browser operation; codexless install/update work.

How do I install Codexless Browser Repair in Claude Code?

Run `npx skills add liyana31811/Codexless --skill codexless-browser-repair -a claude-code`. Or copy the skill folder (skills/codexless-browser-repair in liyana31811/Codexless) into .claude/skills/codexless-browser-repair in your project. Claude Code loads it when a task matches its description.

How do I install Codexless Browser Repair in Codex?

Run `npx skills add liyana31811/Codexless --skill codexless-browser-repair -a codex`. Or copy the skill folder (skills/codexless-browser-repair in liyana31811/Codexless) into .agents/skills/codexless-browser-repair in your project. Codex loads it when a task matches its description.

Can I use Codexless Browser Repair 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 liyana31811/Codexless --skill codexless-browser-repair -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codexless-browser-repair, .gemini/skills/codexless-browser-repair, .github/skills/codexless-browser-repair and .opencode/skills/codexless-browser-repair in your project.

What does Codexless Browser Repair need to run?

SKILL.md names no scripts, command-line tools or credentials: Codexless Browser Repair is instructions for the agent only.

Does Codexless Browser Repair access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Codexless Browser Repair 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 Codexless Browser Repair use?

Codexless Browser Repair is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codexless Browser Repair use?

About 2.2k tokens (SKILL.md is roughly 8.7k 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 Codexless Browser Repair?

Skills that share tags, products or a category with Codexless Browser Repair: Codex with ChatGPT Planning Loop (XiaoDuoYa/codex-with-chatgpt, 7.2k stars), Cao MCP Apps (awslabs/cli-agent-orchestrator, 1.4k stars), Chatgpt Apps (Haohao-end/openagent, 791 stars) and Chatgpt App Builder (alpic-ai/skybridge, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codexless Browser Repair?

liyana31811 (a GitHub user) maintains it in liyana31811/Codexless, which has 118 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 29, 2026.

Source: liyana31811/Codexless on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.