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/start)<a href="https://agentmods.dev/commands/fcakyon/claude-codex-settings/start"><img src="https://agentmods.dev/badge/commands/fcakyon/claude-codex-settings/start.svg" alt="Measured on agentmods" 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.00182 |
| Opus 5 | $0.00000 | $0.00091 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
start 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 3d 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-start
Starts the Supabase local development stack.
Requires supabase/config.toml to be created in your current working directory by running supabase init.
All service containers are started by default. You can exclude those not needed by passing in -x flag. To exclude multiple containers, either pass in a comma separated string, such as -x gotrue,imgproxy, or specify -x flag multiple times.
It is recommended to have at least 7GB of RAM to start all services.
Health checks are automatically added to verify the started containers. Use --ignore-health-check flag to ignore these errors.
If the CLI is running inside a dev container with the Docker socket bind-mounted, set the
SUPABASE_SERVICES_HOSTNAMEenvironment variable to the hostname reachable from inside that container, such ashost.docker.internal.
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.
- 3d ago First seen · 14 lines · 0 tokens per session scan A 97ebc7ab3ee1
start is a command published in the GitHub repository fcakyon/claude-codex-settings (1,130 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 182 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
evaluate
Evaluate a skill across model tiers using blind testing.
start
Turn this freshly cloned template into my project. Run the workflow in docs/playbooks/start.md: welcome me, run a short conversational interview (idea, background, goals, mode, stack, pace), then write PROJECT.md, the design skeleton, and the roadmap in docs/progress.md, and offer to write my first milestone. Keep it…
analyze
Comprehensive LVMS troubleshooting - analyzes LVMCluster, volume groups, PVCs, and storage issues on live clusters or must-gather.
lassare-slack
Switch to Slack mode - questions sent to your Slack DM.
sync-validate
Validate Claude MCP schema and target capability compatibility before syncing.
start
Start AutoGrind — continuous auto-work mode.