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-issuegit 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-issue)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/create-issue"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/create-issue/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-issue"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/create-issue.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.00044 | $0.00479 |
| Opus 5.5 | $0.00018 | $0.00192 |
| Sonnet 5.5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
create-issue 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or revise an issue
An issue describes a problem or missing capability. A PR describes a proposed change. Keep their writing rules separate. For PRs, use create-pr.
Title
Use a concise statement of the problem, naming the affected behavior. Do not use an imperative change request such as "Fix", "Add", "Enable", or "Keep" as the default.
- "Visitor country is unavailable to upstream apps"
- "GeoIP data becomes stale on running installations"
- "Login returns to the wrong page after checkout"
Body
Follow the repository's issue template and the user's requested format. Otherwise use:
## Problem
One or two sentences naming the failure and its effect.
## Reproduction
1. The relevant setup or version.
2. The smallest steps that demonstrate the problem.
## Current behavior
What was observed, with a short error or result when useful.
## Desired behavior
The outcome the reporter needs.
For a missing feature, reproduce the current workflow that exposes the gap. If the problem was not reproduced, say so instead of inventing steps or results. Add environment details, evidence, or a proposed approach only when they help a maintainer act. Keep a possible implementation separate from the desired outcome.
Remove repeated explanations, promotional claims, conversation history, full diagnostic dumps, and details that do not help reproduce or resolve the issue. A few useful sections are better than a long narrative or a checklist of every investigation step.
Publish or update
Inspect repository guidance and templates, search for an existing issue, and verify the claims before publishing. When revising, read the current issue and preserve useful attachments, links, and user edits. Do not expand an issue's scope without user direction.
Use gh issue create or gh issue edit with --title and --body-file. Read back the
published title and body. Link related PRs, but use a closing reference only when the PR
addresses the issue's complete desired outcome.
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.
- yesterday First seen · 57 lines · 44 tokens per session scan A 58f26dfdbf90
create-issue is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,193 stars, last pushed today), licensed Apache-2.0. It adds 44 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-10-29.
Other skills, from other repositories
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-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…
lov-atom-feature-dev
An end-to-end workflow for building a small, self-contained feature across its shared core, command-line tool, API, user interface, saved parameter presets, agent tool, and debugging panel. It uses one contract and shared test cases across the pieces.
lov-plane-cli
A command-line assistant for reading and writing Plane, a project-management system for projects, work items, cycles, modules, statuses, and labels. It connects to a self-hosted or cloud Plane instance through its API.
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
lov-read-codex-session
A read-only tool for inspecting a local Codex task or conversation, including recent progress, tool activity, status, and results. Codex is a coding-agent environment where work is recorded in task threads.