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 seo-auditgit 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/seo-audit)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/seo-audit"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/seo-audit.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.00041 | $0.00804 |
| Opus 5 | $0.00020 | $0.00402 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
seo-audit 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:
- seo-audit — 95% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO audit
Audit in priority order, because the layers depend on each other. A page that can't be indexed doesn't benefit from a better title.
- Can it be found and indexed? Robots rules, canonical tags, noindex, redirect chains.
- Is the foundation sound? HTTPS, mobile rendering, speed, URL structure.
- Is the page optimized? Title, meta description, headings, keyword alignment, internal links, images.
- Does it deserve to rank? Depth, first-hand experience, sourcing, whether it beats what already ranks.
- Does it have credibility? Who links to it, who cites it.
Work down the list and stop where the evidence stops. Most asks are answered at layers 3 and 4.
What a fetch can and can't tell you
web_fetch returns the server's HTML as text. Everything you report as observed has to come from that, from a source you read, or from the caller.
Readable from a fetch: title tag, meta description, heading order and text, body copy, visible links and their anchor text, canonical tag, robots meta, hreflang in the HTML head, server-rendered JSON-LD, robots.txt and sitemap.xml when you fetch them directly.
Not readable, so not yours to assert: anything JavaScript injects after load, Core Web Vitals and any speed measurement, whether Google has actually indexed a URL, rank position, search volume, traffic, backlink counts, and whole-site facts like orphan pages or crawl budget that need a crawl you can't run.
The trap worth naming: CMS SEO plugins commonly inject JSON-LD client side, so a fetch shows no schema on a page that has plenty. Never conclude "no schema" from a fetch. Report that the server HTML carried none, and send them to the Rich Results Test at https://search.google.com/test/rich-results, which renders JavaScript.
For a check you can't run, name the check and the tool rather than skipping it silently. Search Console covers index coverage and queries; PageSpeed Insights covers Core Web Vitals; a crawler like Screaming Frog covers site-wide structure.
What ships with it
2 files 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 · 49 lines · 41 tokens per session scan A 550040d93f89
seo-audit is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,130 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 804 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
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github
Create issues, PRs, clone repos, and manage git workflows.
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-publish-event-onto-hdx
A tool for diagnosing how an event appears on Huodongxing, a Chinese event-listing website. It checks the event’s category, tags, visibility, and ranking.
dsh-plugin-publisher
A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.
lov-skill-pricing
A pricing workflow for creating an explanation-backed pricing card for an AI agent skill. It considers creation and maintenance effort, user value, scarcity, buyer confidence, and distribution potential.