claude-codex-settings
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
Not yet testedsource: 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 has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
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.
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
No recorded runs.
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.
[](https://argusic.com/subject/claude-codex-settings)Questions
- Does claude-codex-settings run?
- claude-codex-settings has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test claude-codex-settings?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for claude-codex-settings?
- All 0 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.