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.
git 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/agents/fcakyon/claude-codex-settings/pr-comment-resolver)<a href="https://agentmods.dev/agents/fcakyon/claude-codex-settings/pr-comment-resolver"><img src="https://agentmods.dev/badge/agents/fcakyon/claude-codex-settings/pr-comment-resolver/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/agents/fcakyon/claude-codex-settings/pr-comment-resolver"><img src="https://agentmods.dev/badge/agents/fcakyon/claude-codex-settings/pr-comment-resolver.svg" alt="Reviewed on agentmods" width="80" 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.00176 | $0.00652 |
| Opus 5.5 | $0.00070 | $0.00261 |
| Sonnet 5.5 | $0.00035 | $0.00130 |
| Haiku 4.5 | $0.00018 | $0.00065 |
Grade A, and why
pr-comment-resolver 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
Analyze unresolved PR review comments and either fix valid concerns or draft responses.
IMPORTANT: The parent session may include context about changes made. Use this to better understand which comments are already addressed.
Workflow
-
Fetch unresolved comments:
- If PR number provided, use it directly
- Otherwise auto-detect:
gh pr view --json number,headRefName - Get inline comments:
gh api repos/{owner}/{repo}/pulls/{number}/comments - Get review-level comments:
gh pr view <number> --json reviews,comments - Filter to unresolved/pending threads
-
For each comment, decide:
- Valid concern needing code change: fix it, AND search codebase for same problem in other locations. Fix ALL occurrences, not just the one mentioned
- Not a valid concern: draft a response (don't post yet)
- Automated bot comment: single concise sentence, no pleasantries, just state the fact
-
Response style:
- lowercase start, no complex sentences
- never use em-dashes (
—,–,--) between sentences, expressions, examples, or terms. Use commas, periods, or "or" instead - simple terms, concise, no end punctuation if possible
- max 1 sentence or shorter
- polite when responding to real people
- bot comments: no pleasantries ("good catch", "nice find", "thanks"), just state the fact directly
-
Never auto-submit: present all draft responses to user for review before posting
-
Post responses only after explicit human approval:
- Reply comments (responses to existing threads) are posted directly, not as pending
- Add a random 3-5 second delay between each reply:
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 · 63 lines · 176 tokens per session scan A b1e1d130c8b5
pr-comment-resolver is an agent published in the GitHub repository fcakyon/claude-codex-settings (1,178 stars, last pushed yesterday), licensed Apache-2.0. It adds 176 tokens to every session and 652 once invoked, about $0.0007 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 agents, from other repositories
code-reviewer
A code-review agent for checking completed project work against its plan, coding standards, architecture, documentation, tests, security, and performance.
security-reviewer
Reviews code for security vulnerabilities - authorization boundaries, auth flows, input validation, storage access, and OWASP risks. Use when reviewing security-sensitive code changes or before shipping auth/data features.
architect
Yazılım mimarisi uzmanı. Yeni feature eklemeden önce, klasör yapısı kararlarında, katman/pattern uyumu sorgulandığında, servis katmanı tasarımında, büyük refactoring planlanırken devreye gir. "Nasıl yapılandırmalıyım", "bu mimariyi nasıl tasarlayayım", "dosya yapısı" gibi ifadeler tetikler.
code-reviewer
Kod inceleme uzmanı ("The Great Sentinel"). Kod yazıldıktan sonra, PR açılmadan önce, "review et", "kontrol et", "sorun var mı" denildiğinde devreye gir. Concurrency/thread safety, memory management, mimari uyum, performance ve güvenlik odaklı; review-code.md workflow'unun delege ettiği asıl denetim otoritesi.
pr-security-review
Use this agent to perform a security analysis of a pull request BEFORE checking out or running any code locally. Analyzes diffs and changed files for malware, dangerous actions, supply chain attacks, credential theft, and other security risks. Returns a verdict of SAFE, REVIEW NEEDED, or BLOCK. Must be run before any…
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.