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 frontend-testing-debugginggit 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/frontend-testing-debugging)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/frontend-testing-debugging"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/frontend-testing-debugging/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/frontend-testing-debugging"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/frontend-testing-debugging.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.00076 | $0.01982 |
| Opus 5.5 | $0.00030 | $0.00793 |
| Sonnet 5.5 | $0.00015 | $0.00396 |
| Haiku 4.5 | $0.00008 | $0.00198 |
Grade A, and why
frontend-testing-debugging 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- frontend-testing-debugging — 91% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Testing Debugging
Invocation Contract
This skill should work from normal user prompts. Do not require the user to spell out Browser routing, screenshots, report shape, or fallback policy.
Use this skill when the user asks to use the Frontend Design Skills plugin, web dev plugin, frontend dev plugin, or frontend testing/debugging skill for a rendered frontend change, test, or bug investigation.
Examples that should trigger this full workflow:
please make an improvement to the web dashboard transaction search area and use the web dev pluginuse the frontend dev plugin to polish this dashboarddebug this UI with the Frontend Design Skills plugintest this localhost app and fix the broken interaction
From a brief prompt, infer the target surface from the repo, currently open app/browser URL, nearby files, or running dev server. If the target URL is unclear, inspect the repo scripts and running local ports before asking the user.
For any code change to a rendered frontend surface, do the validation loop by default:
- Identify the target flow.
- Choose the Browser path below.
- Make the smallest useful edit.
- Validate the rendered behavior.
- Reply with the QA final response report.
Choose The Browser Path
First classify Browser availability:
- Available: the Browser plugin and its
browserskill are listed in the session. Read and follow that skill before any browser action. - Absent: the Browser plugin or
browserskill is not listed. Use regular Playwright and recordBrowser plugin not available. - Invocation failed: Browser appears available, but the skill/runtime, Node REPL JavaScript setup, tab acquisition, or navigation fails. Treat this as a Browser-path blocker.
Do not use regular Playwright, external Chrome, or shell open first when Browser is available.
Only switch from a failed Browser invocation to regular Playwright if the user already allowed fallback or the task explicitly permits non-Browser validation. In that case, report the exact Browser failure and the fallback decision.
What ships with it
1 file 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.
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.
- 3d ago First seen · 143 lines · 76 tokens per session scan A 17846d800214
frontend-testing-debugging is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,181 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,982 once invoked, about $0.0003 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-15.
Other skills, from other repositories
lov-align-wechat-uiux
A WeChat compatibility guide for finding and fixing differences between your product and WeChat's messages, chats, contacts, Moments, and interactions. It traces problems from stored data and message meaning through the interface.
chisle-audit
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in…
Dark Mode Bug Finder
Detect dark mode rendering issues including contrast failures, missing theme tokens, image inversions, and transition glitches across components.
lov-maintain-partners
Maintain the Skill Publisher website's partners section AND align partner logo rows on event posters / hero strips: reuse lov-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets…
lov-app-professional-design
A performance architecture workflow for desktop, web, and mobile apps that examines startup, data loading, front-end and back-end responsibilities, caching, updates, and controlled parallel work. It is intended for diagnosing and repairing slow or repeatedly reloading applications.
lov-app-optimizer
An evidence-based performance investigation method for interactive apps such as Electron, Tauri, mobile apps, and Web/PWA apps. It compares a real workload before and after changes while examining delays, CPU, memory, battery use, background work, and leaks.