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 update-pr-summarygit 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/update-pr-summary)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/update-pr-summary"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/update-pr-summary/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/update-pr-summary"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/update-pr-summary.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.00043 | $0.00376 |
| Opus 5.5 | $0.00017 | $0.00150 |
| Sonnet 5.5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
update-pr-summary 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 14d 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
Update PR Summary
Update a PR title and body to describe the final change and evidence. Treat extra invocation text as the PR reference and any requested corrections.
- Read repository guidance and fetch the current body before editing:
gh pr view <pr> --json title,body,baseRefName,headRefName,url. - Review the complete PR diff against its actual base, not this checkout's unrelated HEAD.
Use
git diff <remote>/<base>...<head>when those refs are current, otherwisegh pr diff <pr>. Ignore changes outside the PR and collect completed checks relevant to its current head. - Read create-pr for title, body, evidence, and visual-hosting guidance. Apply the user's correction to the relevant portion. Preserve uploaded visuals, bot-added context, links, and valid results. An explicit full rewrite still keeps those unless the user asks to remove them. Rewrite stale claims and titles around the final scope.
- Save the exact body to a temporary file outside the repo. Re-read the remote body just
before writing. If it changed, incorporate those edits rather than overwriting them.
Apply with
gh pr edit <pr> --title "..." --body-file <path>. - Read back
title,body,urland compare with the intended edit. Verify that preserved content, fences, tables, and links survived. Open the PR to check media rendering when relevant. Report the PR URL and any remaining evidence or upload gap.
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.
- 14d ago Changed · -6 lines 78125252327d
- 1mo ago First seen · 32 lines · 43 tokens per session scan A b2bb62aca3ae
update-pr-summary is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,186 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 376 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.