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.
npx skills add fcakyon/claude-codex-settings --skill site-architecturegit 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/skills/fcakyon/claude-codex-settings/site-architecture)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/site-architecture"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/site-architecture.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.00046 | $0.01225 |
| Opus 5 | $0.00023 | $0.00613 |
| Sonnet 5 | $0.00009 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
site-architecture 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- site-architecture — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site architecture
Architecture is one decision repeated: how does someone get from the homepage to the page that answers their question, and how does a crawler follow the same path. Depth, navigation, URLs, and internal links are four views of that one structure, so change them together or they drift.
Depth
Aim to put any page that matters within three clicks of the homepage. It isn't a law, but a critical page four or more levels down is a symptom worth chasing.
| Shape | Fits | Costs |
|---|---|---|
| Flat, 2 levels | Small sites, portfolios | Stops scaling once a nav item has 20 children |
| Moderate, 3 levels | Most SaaS and content sites | Usually the right answer |
| Deep, 4 or more | Large catalogs, big docs | Scales, but buries things without strong linking |
Go as flat as the navigation tolerates. When a dropdown passes roughly 20 items, that's the signal to add a level rather than keep the list flat.
Levels: L0 is the homepage, L1 is a primary section (/features, /blog), L2 is a page within it (/features/analytics), L3 and beyond are detail pages (/docs/api/authentication).
Site types as starting points
| Type | Depth | Sections | URL shape |
|---|---|---|---|
| SaaS marketing | 2 to 3 | Home, Features, Pricing, Blog, Docs | /features/{name}, /blog/{slug} |
| Content site | 2 to 3 | Home, Blog, Categories, About | /blog/{slug}, /blog/category/{slug} |
| Ecommerce | 3 to 4 | Home, Categories, Products | /{category}/{subcategory}/{product} |
| Documentation | 3 to 4 | Home, Guides, Reference | /docs/{section}/{page} |
| SaaS plus content | 3 to 4 | Home, Product, Blog, Resources, Docs | /product/{feature}, /blog/{slug} |
| Small business | 1 to 2 | Home, Services, About, Contact | /services/{name} |
URLs
Readable, lowercase, hyphenated, mirroring the hierarchy, with one trailing-slash policy enforced everywhere. Short but still descriptive: /blog/landing-page-conversions beats /blog/how-to-improve-your-landing-page-conversion-rates.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 78 lines · 46 tokens per session scan A e9cac502083b
site-architecture is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,130 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,225 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
lov-app-generator
An app-building workflow that creates or upgrades web apps, Tauri desktop apps, or native macOS apps from a project brief. Tauri packages a web-based interface as a desktop application.
lov-maintain-partners
Maintain the Skill Publisher website's partners section AND align partner logo rows on event posters / hero strips: reuse lov-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets…
lov-install-tanstack-query
Initialize or refactor a frontend project to use TanStack Query as the unified server-state layer. Use when the user asks to install TanStack Query, initialize query infrastructure, migrate ad hoc fetch/invoke/useEffect request state, standardize query keys, or make app network requests share one cache model. Also…
lov-integrate-lovinsp
A setup and migration guide for Lovinsp, a development feature that lets you click an element in a browser and jump to its source code.
lov-mobile-adapt
A mobile adaptation workflow for existing web projects. It adjusts desktop websites for phones by handling responsive layouts, overflow, safe areas around notches, browser viewport height, touch targets, and mobile navigation.
lov-oh-my-landingpage
A landing-page creation and redesign skill that derives a product’s positioning, story, and visual direction from its actual product and brand facts. It then implements the page responsively and checks the result against the intended product message.