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/codex-advisornpx skills add fcakyon/claude-codex-settings --skill codex-advisorgit clone --depth 1 https://github.com/fcakyon/claude-codex-settingsWhat 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 | $0.00053 | $0.00346 |
| Opus 5 | $0.00026 | $0.00173 |
| Sonnet 5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
codex-advisor 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.
What it actually says
Codex Advisor
Get a focused second opinion from GPT through the Codex CLI, without handing the work over to it.
Route by tool
-
In Claude Code, delegate to the native
codex-advisoragent. It receives the recent conversation automatically, so do not paste the history yourself. -
Elsewhere, run this exact shape from this skill's directory so the request reaches standard input:
node scripts/ask_codex.mjs <<'REVIEW' the review request REVIEW
State the decision, the evidence behind it, and any constraint that changes the verdict. Name the paths that matter: the reviewer has read-only access and checks load-bearing claims itself.
Return the answer without rewriting it. If codex is missing or unauthenticated,
surface the error and ask the user to install it or sign in. Never review in its
place.
Reviewer
Pinned to gpt-5.6-sol at medium reasoning effort. Inside Codex that may be the
model already doing the work, so set CODEX_ADVISOR_MODEL to a different one.
Weighing the answer
Give the verdict serious weight. If a step it recommends fails when tried, or a file contradicts a specific claim, surface the conflict instead of following the review blindly.
What ships with it
2 files 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 · 42 lines · 53 tokens per session scan A 2fd371da218b
codex-advisor is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,117 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 346 once invoked, about $0.0003 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.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace. Use when the user asks to inspect Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cline, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, or generic JSON/JSONL traces for cost, tokens, tool failures, latency…
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 插件。.
deep-research
Use when the user needs multi-source research with citation tracking, evidence persistence, structured report generation, or an implementation landscape that includes GitHub and other open-source forges. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends"…
lov-env-management
统一管理平台、账号与多组 API Key，维护有效期和启用状态，安全同步到 zsh 或用户会话环境，并提供脱敏 Dashboard；用户说“管理环境变量”“rotate API keys”时使用。.
lov-gh-access
Open a private GitHub repo to external clients or contractors without making it public. Accepts a mixed list of GitHub usernames and/or email addresses, resolves each to a GitHub account (falling back to an email invitation when the user has no discoverable account yet), and invites them as collaborators with a chosen…