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/init)<a href="https://agentmods.dev/commands/fcakyon/claude-codex-settings/init"><img src="https://agentmods.dev/badge/commands/fcakyon/claude-codex-settings/init/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/init"><img src="https://agentmods.dev/badge/commands/fcakyon/claude-codex-settings/init.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.00159 |
| Opus 5.5 | $0.00000 | $0.00064 |
| Sonnet 5.5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
init 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 18d 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-init
Initialize configurations for Supabase local development.
A supabase/config.toml file is created in your current working directory. This configuration is specific to each local project.
You may override the directory path by specifying the
SUPABASE_WORKDIRenvironment variable or--workdirflag.
In addition to config.toml, the supabase directory may also contain other Supabase objects, such as migrations, functions, tests, etc.
To use OrioleDB as the Postgres storage engine, run supabase init --use-orioledb. The command writes the OrioleDB version to db.orioledb_version in supabase/config.toml; --experimental is not required.
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.
- 18d ago Changed · +2 lines 4697192c7c64
- 1mo ago First seen · 10 lines · 0 tokens per session scan A cecafd35e733
init is a command published in the GitHub repository fcakyon/claude-codex-settings (1,181 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 159 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
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
integrate
Start the Integration Architect lifecycle. Runs the 5-phase deterministic workflow (Discovery → UI Analysis → Contract Design → DB Alignment → Quality).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.