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 agentmods add skills/fcakyon/claude-codex-settings/writing-guidelinesnpx 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.svg" alt="Measured on agentmods" 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.00034 | $0.03390 |
| Opus 5 | $0.00017 | $0.01695 |
| Sonnet 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 6d 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.
- 6d 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,127 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 3,390 once invoked, about $0.0002 per session on Opus 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.
github
Create issues, PRs, clone repos, and manage git workflows.
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-publish-event-onto-hdx
诊断并修改活动行已发布活动：核查分类页可见性与排名、替换详情正文配图，并守住 后台保存会清空分类这一平台陷阱。Trigger: 活动行分类找不到、活动行分类没了、 活动行排名、活动行曝光、活动行换海报、hdx category not showing, hdx category reset。.
dsh-plugin-publisher
Publish a validated DSH plugin package (@deepseek-ai/dsh- or @lovstudio/dsh-) to npm, git, or tarball channels and verify it loads in the DeepSeek Harness. Use when the user asks to publish, release, or ship a plugin. 触发：发布插件 / 上架插件 / release dsh 插件。.
lov-npm-publisher
为全新或已有 npm 包建立免重复登录的自动发布链，兼容 GitHub Actions OIDC（trusted publishing）与本地 granular NPMTOKEN（bypass）两种平级方式，处理首次引导、发布审计与线上回读。Use when the user asks to 自动发布 npm 包、publish npm without login、发布 npm 包不用登录。.