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 operating-livekit-agentsgit 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/operating-livekit-agents)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/operating-livekit-agents"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/operating-livekit-agents/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/operating-livekit-agents"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/operating-livekit-agents.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.00178 | $0.02179 |
| Opus 5.5 | $0.00071 | $0.00872 |
| Sonnet 5.5 | $0.00036 | $0.00436 |
| Haiku 4.5 | $0.00018 | $0.00218 |
Grade A, and why
operating-livekit-agents 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 26d 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:
- operating-livekit-agents — 94% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating LiveKit agents
Everything after the agent works: getting a version onto LiveKit Cloud, keeping it fast and alive
under real load, and changing it without breaking what's already running. The commands live under
lk agent; read lk agent --help and each subcommand's help rather than trusting this skill for
flags — it deliberately doesn't restate them. reading-livekit-docs has the deployment and
observability docs.
Deploying to LiveKit Cloud
On a self-hosted LiveKit server the lk agent deploy commands do not apply. Ship the agent as a
container or process under your own tooling (Docker, Kubernetes, systemd), keep secrets in its
environment, and look up the server side with lk docs get-page /home/self-hosting. The worker,
shutdown, and observability guidance below applies either way.
The shape is stable even as the flags move:
- A project directory is bound to an agent by a config file the CLI writes (
livekit.toml). Commands run from that directory find the agent without an id. - The agent ships as a container. The CLI can generate a Dockerfile for the project, or you
bring a prebuilt image. Run the container's start command locally (
lk agent start) before the first deploy — it's production mode, with production logging and a shutdown drain, and it is not whatdevmode runs. - Each deploy creates a version and rolls it out.
status,versions, andlogs(build logs and deploy logs are separate) tell you what's live and why a rollout failed. - Secrets are injected as environment variables and managed apart from the code — never baked into the image or committed. Changing secrets restarts the agent.
- Rollback returns to a previous version. How instant that is depends on the plan; the docs say. Know the rollback command before you need it.
After a deploy, verify with the same tools you'd use on a stranger's agent: status for the
rollout, logs for the first minutes, and a real conversation — running-livekit-simulations can
run a scenario file against the deployed agent by name, which is the cheapest end-to-end check that
the thing serving traffic is the thing you meant to ship.
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.
- 26d ago First seen · 163 lines · 178 tokens per session scan A 5cfc56b6601d
operating-livekit-agents is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,191 stars, last pushed yesterday), licensed Apache-2.0. It adds 178 tokens to every session and 2,179 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-10-02.
Other skills, from other repositories
lov-deploy-to-vercel
A deployment workflow for publishing Vite, Next.js, Create React App, or static frontend projects on Vercel, a hosting service for web applications. It can also connect a custom domain and configure Cloudflare DNS records.
lov-domain-cutover
A workflow for putting a mainland-China website online after its ICP filing is approved. It verifies the deployment, DNS, HTTPS certificate, domain response, ICP footer, and handling of the old domain.
netdata-mcp-integration
Use when an AI coding agent needs to connect to a Netdata Agent, Parent, or Netdata Cloud via MCP to verify telemetry, query live metrics, cross-reference instrumentation with infrastructure signals, or troubleshoot services. Covers Claude Code, Cursor, Codex, and Gemini CLI client configs for both local…
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
devops/deploy-cloudflare
A deployment guide for Cloudflare Pages and Workers using the Wrangler command-line tool. Pages hosts frontend and static sites, while Workers runs serverless code and APIs at Cloudflare's edge locations.