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 connect-recommendgit 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/connect-recommend)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/connect-recommend"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/connect-recommend/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/connect-recommend"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/connect-recommend.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.00151 | $0.04950 |
| Opus 5.5 | $0.00060 | $0.01980 |
| Sonnet 5.5 | $0.00030 | $0.00990 |
| Haiku 4.5 | $0.00015 | $0.00495 |
Grade A, and why
connect-recommend 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 18d 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.
This is a copy
98% identical to connect-recommend — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect recommend
Recommend the right Stripe Connect integration configuration. The user only needs to provide a company URL or describe their business — the skill figures out the rest.
Interaction model
User must confirm interactions. Every decision point in this skill MUST be confirmed with the user with clear, numbered options and short descriptions. One question at a time — never overwhelm the user.
Auto-act on low-cost actions. Never ask permission for:
- Generating the markdown recommendation plan — just generate it
- Scanning the codebase — just scan it
- Reading reference files — just read them
Never end with passive text. Every stopping point must end with a prompt to the user offering concrete next actions.
Terminology rules (user-facing output)
Before generating any user-facing output, read references/terminology-rules.md. Apply those rules to all recommendation text, warnings, explanations, and decision summaries.
Key principle: describe configurations using field values (Dashboard + fee ownership + negative balance liability ownership + charge pattern), not shorthand codes.
Output Brevity
Keep responses concise. The user is making decisions, not reading documentation.
- Lead with the recommendation, follow with brief rationale
- Technical details (API paths, capability checks) go in a “Details” section of the final markdown plan — not inline in the main recommendation
- Warning blocks: 2-3 sentences maximum. State the issue and the fix. No mechanism deep-dives unless the user asks.
- Decision summary: bullet points only, one line per decision
- Never output more than ~40 lines in a single response during interactive mode
Only mention out-of-scope limitations when they’re directly relevant to what the user asked about. Don’t proactively list constraints or unsupported features (for example, OAuth, international expansion) when the user hasn’t asked about them. “Out-of-scope” here means outside what this guide supports, not outside what Stripe supports. Research these topics in the Stripe public documentation (docs.stripe.com) rather than saying they’re out-of-scope.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/account-types.md 19 KB
- references/charge-patterns.md 12 KB
- references/company-researcher.md 7.6 KB
- references/compatibility-matrix.md 17 KB
- references/decision-matrix.md 38 KB
- references/discovery-questions.md 20 KB
- references/recommendation-template.md 17 KB
- references/terminology-rules.md 8.9 KB
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.
- 18d ago First seen · 362 lines · 151 tokens per session scan A 7217199b98ba
connect-recommend is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,181 stars, last pushed today), licensed Apache-2.0. It adds 151 tokens to every session and 4,950 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to connect-recommend, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
lov-skill-pricing
A pricing workflow for creating an explanation-backed pricing card for an AI agent skill. It considers creation and maintenance effort, user value, scarcity, buyer confidence, and distribution potential.
lov-expense-report
A tool that reads invoice photos, scanned receipts, or expense descriptions and turns them into a categorized Excel reimbursement report. It extracts details such as date, vendor, item, amount, and notes.
ainb-fleet:cost
Show fleet spend — per-session, per-model, per-day, and per-group USD cost rollups for every claude/codex session, sourced live from ainb's burndown analytics (which already prices every provider call). Use when you need spend visibility across a multi-session fleet, want to find the most expensive session/model, or…
payment-gateways-stripe-adyen-integration
Architect and implement secure, PCI-DSS compliant payment processing integrations with Stripe and Adyen, featuring idempotent webhook handling, tokenization, multi-currency processing, automatic retries, and ledger-based reconciliation.
tray-pagamentos
API de informações de pagamento da Tray (recurso payments). Cobre listar, consultar, criar, atualizar e excluir registros de pagamento (CRUD em /payments), além de consultar as opções de pagamento ativas da loja (/payments/options) e as configurações globais de pagamento (/payments/settings). Total de 7 endpoints.…
tray-notas-fiscais
API de Notas Fiscais (NF-e) da Tray. Utilize quando o desenvolvedor precisar gerenciar notas fiscais eletrônicas associadas a pedidos, incluindo listagem geral, consulta por ID, consulta por pedido, criação e atualização. Inclui campos como número, série, chave de acesso, CFOP, link do DANFE e valor total, essenciais…