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.
git 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/plugins/fcakyon/claude-codex-settings/claude-tools)<a href="https://agentmods.dev/plugins/fcakyon/claude-codex-settings/claude-tools"><img src="https://agentmods.dev/badge/plugins/fcakyon/claude-codex-settings/claude-tools/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/plugins/fcakyon/claude-codex-settings/claude-tools"><img src="https://agentmods.dev/badge/plugins/fcakyon/claude-codex-settings/claude-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-tools 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 5d 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.
What it actually says
{
"name": "claude-tools",
"version": "2.1.5",
"description": "Sync CLAUDE.md and the permissions allowlist, and refresh context on demand.",
"author": {
"name": "Fatih C. Akyon"
},
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 3 commands travel with it, and installing the plugin installs all of them — 32 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed ee77e4d82951
- 1mo ago First seen · 10 lines scan A 3107fd0a96f8
claude-tools is a plugin published in the GitHub repository fcakyon/claude-codex-settings (1,192 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
general
General — 32 free skills bundled together.
content-creation
Content Creation — 15 free skills bundled together.
video-creation
Video Creation — 11 free skills bundled together.
meta
Meta — 7 free skills bundled together.
ainb-fleet
LLM-facing skill teaching agents how to spawn ainb sessions correctly and how to use ainb fleet ... orchestration subcommands. Spawning covers the ainb run contract (always into a git worktree, plus the --parent shapes that silently misfire). Fleet covers multi-session broadcast, ack-gated sequence, blocked-sessi.
old-craft
A build-planning add-on that studies similar GitHub repositories before new software is created. It also covers sorting priorities, checks, licensing, and setting up a starter project.