claude-codex-settings

Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.

Runssource: GitHubhomepagePythonApache-2.0commit 8c25677efb55

Python, Apache-2.0 licensed. The project labels itself: ai agents, ai tools, claude ai, claude code, claude code plugin, claude skills, claudecode and claudecode config.

claude-codex-settings runs. An Argusic agent installed it in 24 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Codex CLI v0.170.0 installed, marketplace fcakyon/claude-codex-settings added, 5 plugins installed (simplify, python-skills, github-dev, stripe-skills, livekit-skills) with all enabled, plugin validation passes 34 plugins, all 3 test suites pass (26/26 total), sync scripts run (stripe, mongodb, hetzner, polar) with only zip missing as non-critical, site build blocked by old Node.js

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
2
last tested
stars
1,217
forks
116
open issues
4
watchers
8
size
7 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing claude-codex-settings, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • slides_test.py missing pdf2image and pdftoppm2 minutes
  • polar sync had stale checkout on first run (empty master branch)1 minute
  • zip command not available in container
  • Node.js v18.19.1 too old for Astro site build (needs >=22.12.0)
Install time
24 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
codex exec --ephemeral 'echo hello' ran successfully via OpenRouter mock proxy, codex exec review --uncommitted ran successfully, python3 validate_plugins.py exited 0, python3 test_simplify_guard.py: 8/8 passed, python3 test_humanize.py: 16/16 passed, python3 test_require_visual_proof.py: 2/2 passed, codex plugin list shows 5 installed+enabled plugins, codex doctor reports 19 ok 0 fail
Model tokens used
108,508
Exact commit tested
8c25677efb55
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    def setUp(self) -> None:
        """Create a repository whose integration branch contains a design change."""
exec
/bin/sh -lc 'cd /work/repo && python3 -u .github/scripts/test_require_visual_proof.py 2>&1 | head -…
 succeeded in 161ms:
..
Ran 2 tests in 0.241s
OK
All tests pass. Let me compile the full report.
tokens used
108,508
All tests pass. Let me compile the full report.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 24 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.

Of the 124 ai-agents projects Argusic has installed and timed, claude-codex-settings was the 108th fastest to reach a running state, and 96 of 124 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.05
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

ai-agentsai-toolsclaude-aiclaude-codeclaude-code-pluginclaude-skillsclaudecodeclaudecode-configcodexcodex-clicommit-messagecursorfrontend-designgemini-cligithubhetznerkimi-k3openshippluginpull-requests

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/claude-codex-settings.svg)](https://argusic.com/subject/claude-codex-settings)

Questions

Does claude-codex-settings run?
Yes. claude-codex-settings runs. Argusic installed and launched it on a clean machine in 24 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test claude-codex-settings?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8c25677efb55. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test claude-codex-settings?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does claude-codex-settings take to install?
24 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does claude-codex-settings need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing claude-codex-settings?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does claude-codex-settings compare with the alternatives?
Of the 124 ai-agents projects Argusic has installed and timed, claude-codex-settings was the 108th fastest to reach a running state, and 96 of 124 reached one at all.
Where is the evidence for claude-codex-settings?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion