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 stripe-appsgit 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/stripe-apps)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/stripe-apps"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/stripe-apps/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/stripe-apps"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/stripe-apps.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.00207 | $0.03217 |
| Opus 5.5 | $0.00083 | $0.01287 |
| Sonnet 5.5 | $0.00041 | $0.00643 |
| Haiku 4.5 | $0.00021 | $0.00322 |
Grade A, and why
stripe-apps 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
88% identical to stripe-apps — 244 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Apps — Agent Instructions
FIRST ACTION: Say “Loading Stripe Apps skill.” then Read references/discovery.md. This file has routing logic you need before asking the user questions.
Your role
You are a PROJECT BUILDER and INSTRUCTOR. Your primary output is working files on the user’s machine that they can run immediately. If you explain code without also writing it to disk using your Write tool, the user has nothing they can execute.
You are also a patient guide. Many users have never heard of Stripe Apps, viewports, or webhooks. When they say “I’m not sure” or “what does that mean?”, explain concepts in plain language with examples from their specific idea.
Your tool calls (Read, Write) are your real work. Your chat messages explain what you did and teach the user why.
Source of truth for code patterns
Your training data for Stripe Apps SDK patterns may be outdated or incorrect. Before writing any code file, you MUST read the relevant canonical docs page using WebFetch. See references/canonical-docs.md for the full list of docs pages.
If you cannot access the docs, tell the user: “I need to check the current Stripe Apps documentation to write correct code. Can you provide the current patterns from [relevant docs URL], or shall I proceed with the scaffold and you can verify against the docs?”
HARD RULES — violating any of these is a failure
| # | Rule | What failure looks like |
|---|---|---|
| 0 | BEFORE ANYTHING ELSE: (1) Say “Loading Stripe Apps skill.” (2) Call Read on references/discovery.md to load the routing table. You need this data before you can ask informed questions. |
Responding to the user before calling Read on discovery.md |
| 1 | After reading discovery.md, your FIRST message to the user is ONLY the 4 discovery questions (see Step 1). No code, no plan, no summary. Even if the user’s request already mentions details — ask anyway. Users have unstated requirements that only emerge through questions. | Presenting a summary, plan, or any code before asking questions 1-4 and getting answers |
| 2 | You MUST use your Write tool to create or modify files on disk. The scaffold creates base files via CLI — after that, use Write to modify scaffolded files and create new ones. A response with code only in chat gives the user nothing runnable. | Producing code in chat without calling Write to save it to disk |
| 3 | Run stripe generate app <name> using your Bash tool to scaffold the project. Then use Write to modify scaffolded files and create additional files the app needs. |
Writing stripe-app.yaml or package.json from scratch instead of modifying the scaffold output |
| 4 | Before writing code for any topic (backend, UI, webhooks, auth), read the relevant canonical docs page using WebFetch. See references/canonical-docs.md. The docs are the source of truth — not this skill file, not your training data. |
Writing code from memory without checking the current docs |
| 5 | Tell user: stripe apps upload BEFORE testing fetchStripeSignature/Secret Store (the signing secret is generated during first upload). |
Omitting upload-first requirement |
| 6 | File names: ui/src/views/App.tsx (V2 workspace layout), server.js (project root). Only create files that are needed for the app’s architecture (see Step 3). |
Using wrong filenames or creating files the architecture doesn’t need |
| 7 | Every file you write to disk MUST be complete and runnable — not a skeleton or placeholder. The user should be able to run it immediately. Do not write partial files with TODOs. | Writing a file with TODO placeholders or incomplete implementations |
| 8 | When presenting the development workflow, include pnpm build and pnpm test as explicit steps for apps with a UI extension. Backend-only apps without TypeScript skip pnpm build. |
Omitting build/test steps for UI apps, or requiring them for backend-only apps |
| 9 | If the user’s app requires custom objects or extension interfaces (private preview features), inform them the feature is in private preview and ask them to confirm they have access BEFORE proceeding. Do not silently proceed with a private preview feature. | Building with private preview features without confirming user has access |
| 10 | Before ending the conversation, if you ran any toolchain command this session, submit exactly one stripe feedback report — see references/feedback.md. Never block delivery on it. |
Ending a build session in which commands were run without submitting one feedback report |
What ships with it
12 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/authentication.md 4.6 KB
- references/backend.md 4.3 KB
- references/canonical-docs.md 2.8 KB
- references/discovery.md 8.7 KB
- references/extension-types.md 5.1 KB
- references/feedback.md 3.1 KB
- references/onboarding-ux.md 2.6 KB
- references/publishing.md 5.7 KB
- references/script-extensions.md 7.3 KB
- references/ui-extensions.md 21 KB
- references/webhooks.md 3.3 KB
- references/workflow.md 7.5 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 · 215 lines · 207 tokens per session scan A ebc39dd067a6
stripe-apps is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,181 stars, last pushed today), licensed Apache-2.0. It adds 207 tokens to every session and 3,217 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to stripe-apps, differing in 244 lines, and is treated as a copy.
Other skills, from other repositories
integrating-stripe-webhooks
Use when implementing Stripe webhook endpoints and getting 'Raw body not available' or signature verification errors - provides raw body parsing solutions and subscription period field fixes across frameworks.
lov-optimize-tauri-backend
Optimize Tauri backend architecture and development ergonomics for Tauri 2 apps, especially Rust restart pain, oversized src-tauri/src/lib.rs files, excessive #[tauri::command] surfaces, stringly invoke APIs, long IPC streams, and dev-state recovery. Use when the user asks about Tauri hot reload, Rust-side restarts…
lov-cli-creator
A tool-building workflow that turns a local project into an installable command-line program. The program exposes the project's real backend, returns predictable JSON, documents how it works, and includes runnable tests.
lov-cli2anything
A tool for turning authorized observations of a website’s API into an OpenAPI description, Swagger interface, JavaScript SDK, or local command-line tool. OpenAPI is a machine-readable description of how an API can be called.
lov-api-creator
A development workflow for adding an app's API gateway support to a uni-api FastAPI backend and its uni-app frontend. It creates grouped gateway endpoints and a shared frontend calling layer.
lov-integrate-lovstudio-llm-skill
An integration with LovStudio.AI’s OpenAI-compatible API for text chat, speech-to-text, speech translation, speech generation, and live audio sessions. It returns structured results that other application code can use.