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 create-prgit 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/create-pr)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/create-pr"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/create-pr/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/skills/fcakyon/claude-codex-settings/create-pr"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01407 |
| Opus 5.5 | $0.00020 | $0.00563 |
| Sonnet 5.5 | $0.00010 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
create-pr 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Create a PR a reviewer can understand without reading the conversation. Use extra invocation text and session findings to explain the problem, final behavior, and evidence. Follow the user's requested format and the target repo's guidance.
Workflow
-
Inspect the scope and base
- Read repository guidance and inspect
git status, staged changes, and the current branch. - Honor staged-only requests. Never stage unrelated work or require a new commit when the branch already contains the requested changes.
- Confirm the target remote and base branch. Before creating a branch from main/master,
fetch that remote and fast-forward the local base with
git merge --ff-only <remote>/<base>. Preserve dirty work and stop if fast-forwarding fails. Do not reset it away. - Create a short branch using the repo's naming convention. Never commit directly to main.
- Read repository guidance and inspect
-
Finish and inspect the change
- Run
/simplifyon the staged diff before committing and apply its findings. Docs-only diffs are a no-op. Followcommit-stagedfor any staged changes. - Update existing documentation only when the requested change makes it inaccurate.
- Review
git diff <remote>/<base>...HEADacross all commits. For an existing PR, use its actual base and head, orgh pr diff <pr>if this checkout is on another branch. - Run appropriate checks and collect their actual results. Verify session findings against the final change, including links, counts, errors, and benchmark provenance.
- Run
-
Write and publish
- Use the title and body guidance below. If a PR already exists, use
update-pr-summaryrather than opening a duplicate. - Write the exact body to a temporary file outside the repo and pass
--body-filetogh. Never interpolate text into a shell command or include command output by accident. - Push the branch and create with an explicit base,
--title,--body-file, and-a @me. - Add a reviewer only if explicitly requested or recent PRs by this author have reviewers:
gh pr list --repo <owner>/<repo> --author @me --limit 5 --json reviewRequests. - Read back the published title and body with
gh pr view <pr> --json title,body,url. Check code fences, tables, links, and preserved media. For visual changes, open the PR and verify the images render. Report the URL and any incomplete verification.
- Use the title and body guidance below. If a PR already exists, use
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.
- 12d ago Changed · +6 lines e382f97ac225
- 1mo ago First seen · 104 lines · 49 tokens per session scan A 97303d465ceb
create-pr is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,181 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,407 once invoked, about $0.0002 per session on Opus 5.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-08-30.
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.
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-optimizer
Audit and optimize one or more existing Agent Skills from a canonical source path, then bump semver, update README/SKILL.md/skill.yaml/CHANGELOG.md, and verify installed copies and catalog synchronization. Checks frontmatter, trigger quality, CLI hygiene, naming, portability, version drift, dirty worktrees, shared…
lov-rename-project
A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.
lov-gh-access
Open a private GitHub repo to external clients or contractors without making it public. Accepts a mixed list of GitHub usernames and/or email addresses, resolves each to a GitHub account (falling back to an email invitation when the user has no discoverable account yet), and invites them as collaborators with a chosen…
lov-skill-publisher
Publish or submit a validated Skill. Default to the LovStudio official website, run lov-skill-pricing automatically, and use other channels only when explicitly named.