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 writing-guidelinesgit 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/writing-guidelines)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/writing-guidelines"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/writing-guidelines/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/writing-guidelines"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/writing-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.03390 |
| Opus 5.5 | $0.00014 | $0.01356 |
| Sonnet 5.5 | $0.00007 | $0.00678 |
| Haiku 4.5 | $0.00003 | $0.00339 |
Grade A, and why
writing-guidelines 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Guidelines
Review the files or patterns provided by the user for compliance.
Read files, check against rules below. Output concise but comprehensive: sacrifice grammar for brevity. High signal-to-noise.
Rules
Planning & content type
- Every page has a plan (overview, goal, audience, content plan, open questions) referenced or linked
- Content type declared in
meta.contentType:Tutorial,How-to,Reference,Conceptual,Troubleshooting, orLanding - Title is user-shaped (the user's question), not feature-shaped (the engineer's name)
- Page does one job: tutorial OR how-to OR reference, not three at once
- Goal is verb-driven (Bloom's taxonomy): "configure", "explain", "debug" (testable)
- Multi-audience pages: short shared opener, then technical subsections
Voice & tone
- Active voice. Mental test: append "by monkeys". If the sentence parses, rewrite
- Direct address:
you, neverthe userorone can - Imperative for steps: "Click Add Project", not "You will need to click Add Project"
- Sentences under 20 words target
- Contractions encouraged (
you'll,it's) for warmth - Present tense unless describing future behavior
- Limit
we: only for deliberate organization actions ("we recommend", "we deprecated"), never as a stand-in for "you" - No rhetorical questions (sounds like marketing)
- Second-read test: read each sentence once at speech pace; if you re-read to parse it, name the subject, the action, and the consequence (kill metaphor verbs and pronouns reaching back several sentences)
Banned words
easy,simple,quick: puts pressure on the reader and reads as marketing; replace with concrete description ("one command", "default settings", "most projects don't need this")very,just,really: filler; cut or rewrite
Concision
- Earn every detail: cut a number, name, or implementation detail if a more general phrasing wouldn't change the reader's understanding or action
- Weasel words: replace vague qualifiers (
significantly,many,often,typically,generally) with a specific number or claim - Vague quantifiers: no
near-zero,sub-second,most requests; give the figure and cite it (99.37% of requests see zero cold starts) - Filler/metaphor verbs: name the action instead of reaching for cadence (
moves through,lands,carries,hits→ the literal step)
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.
- 1mo ago First seen · 261 lines · 34 tokens per session scan A 77ff8e79a9cf
writing-guidelines is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,183 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 3,390 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
chisle
Maximum-efficiency dev mode: terse zero-fluff prose + YAGNI/ladder-first code. Use when user says "chisle mode", "activate chisle", "chislify", "be efficient", "be minimal", "no fluff", "yagni", or invokes /chisle. Deactivate: "stop chisle" / "normal mode".
dsh-plugin-publisher
A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.
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-media-crawler
A workflow for downloading one publicly accessible video or media post from supported Chinese social platforms to a local file, using existing sign-in access when available.
lov-publish-wechat-channels
A browser-based assistant for checking, uploading, saving, scheduling, and publishing local videos to WeChat Channels, WeChat’s short-video platform. It also verifies the resulting draft or publication status.