claude-codex-settings is a collection of configurations and reusable extensions for Claude Code, OpenAI Codex, Cursor, and related coding tools. Developers use its skills, commands, hooks, agents, plugins, and MCP servers to shape coding-agent workflows and connect alternative model APIs. The catalogue entries are components of this collection that can be installed into supported coding tools.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settingsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/fcakyon/claude-codex-settings/login)<a href="https://agentmods.dev/commands/fcakyon/claude-codex-settings/login"><img src="https://agentmods.dev/badge/commands/fcakyon/claude-codex-settings/login/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fcakyon/claude-codex-settings/login"><img src="https://agentmods.dev/badge/commands/fcakyon/claude-codex-settings/login.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00146 |
| Opus 5.5 | $0.00000 | $0.00058 |
| Sonnet 5.5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
login scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
supabase-login
Connect the Supabase CLI to your Supabase account by logging in with your personal access token.
Your access token is stored securely in native credentials storage. If native credentials storage is unavailable, it will be written to a plain text file at <SUPABASE_HOME or ~/.supabase>/access-token.
If this behavior is not desired, such as in a CI environment, you may skip login by specifying the
SUPABASE_ACCESS_TOKENenvironment variable in other commands.
The Supabase CLI uses the stored token to access Management APIs for projects, functions, secrets, etc.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 10 lines · 0 tokens per session scan A d8d0570ad908
login is a command published in the GitHub repository fcakyon/claude-codex-settings (1,186 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 146 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
start-11-5
A lesson on using GitHub Actions to deploy software and generate files. GitHub Actions is GitHub's system for running automated jobs when code changes.
deploy-check
Pre-flight verification before pushing to main. Reproduces the CI gates locally so the push doesn't fail in production.
evaluate
Evaluate a skill across model tiers using blind testing.
trigger-postsubmit
Trigger a postsubmit gangway job with repository refs.
sync-validate
Validate Claude MCP schema and target capability compatibility before syncing.
sync-list
List all MCP servers configured in Claude Code with transport type and source.