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 resolve-pr-commentsgit 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/resolve-pr-comments)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/resolve-pr-comments"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/resolve-pr-comments/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/resolve-pr-comments"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/resolve-pr-comments.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.00047 | $0.00479 |
| Opus 5.5 | $0.00019 | $0.00192 |
| Sonnet 5.5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
resolve-pr-comments 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 1mo 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
Resolve PR Comments
Analyze unresolved PR review comments, fix valid concerns, and draft responses for comments that do not require code changes.
When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch.
Process
-
Preferred execution
- If subagents are available, use
github-dev:pr-comment-resolverand pass the PR reference. - Otherwise follow the manual steps below.
- If subagents are available, use
-
Fetch unresolved comments
- If a PR number or URL is provided, use it directly.
- Otherwise auto-detect the PR from the current branch with
gh pr view --json number,headRefName. - Fetch inline comments with
gh api repos/{owner}/{repo}/pulls/{number}/comments. - Fetch review-level comments with
gh pr view <number> --json reviews,comments. - Filter to unresolved or pending threads.
-
Resolve each comment
- If the comment is valid, fix the code and search the codebase for the same problem in other locations.
- Fix all matching occurrences, not just the location mentioned in the comment.
- If the comment does not require a code change, draft a concise reply.
- If the comment is from a bot, reply with a direct factual sentence and no pleasantries.
-
Reply style
- Start in lowercase.
- Use simple language and short sentences.
- Avoid end punctuation when possible.
- Be concise and polite when replying to real people.
-
Never auto-submit
- Present all draft responses before posting them.
- Reply comments are posted directly with
gh api repos/{owner}/{repo}/pulls/{number}/comments/{comment_id}/replies -f body="..."(the{number}PR number is required, the endpoint 404s without it). - Add a random 3-5 second delay between posted replies with
sleep $((RANDOM % 3 + 3)).
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.
- 1mo ago First seen · 43 lines · 47 tokens per session scan A 9ffc0e810b13
resolve-pr-comments is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,181 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 479 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.
git-authoring
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…
code-review
Systematic code review SOP covering correctness, security, performance, and maintainability — plus GitHub PR review workflow (diff, inline comments, approve via gh/REST).
pr-reviewer
A pull-request review workflow for checking team-specific coding style, naming, and code structure. A pull request is a proposed change to a codebase that teammates inspect before merging.
pr-monitor
Monitor GitHub repo health — CI failures on main, PRs awaiting review over 24h, PRs with failing checks, stale PRs — and alert. Use when checking repo/PR/CI health, investigating why an alert fired, or adding a repo to watch.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…