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/ldclabs/anda-bot/codexnpx skills add ldclabs/anda-bot --skill codexgit clone --depth 1 https://github.com/ldclabs/anda-botWhat 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.00095 | $0.01745 |
| Opus 5 | $0.00048 | $0.00873 |
| Sonnet 5 | $0.00019 | $0.00349 |
| Haiku 4.5 | $0.00010 | $0.00175 |
Grade A, and why
codex 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex CLI Delegation for Agent's Shell Tool
This skill is written for shell tool. Assume there is no PTY. Do not use interactive Codex TUI flows.
Non-Interactive Rules
- Use
codex execfor every delegated task. - Do not run bare
codex,codex resume, app-server flows, desktop app flows, tmux, or commands that wait for keyboard input. - Do not pass PTY-only options. If older guidance says
pty=true, ignore it in the agent. - Place global flags after the subcommand, for example
codex exec --cd "$PROJECT" .... - Prefer
--sandbox workspace-write --ask-for-approval neverfor implementation tasks. This keeps edits inside the workspace and avoids approval prompts that the shell cannot answer. - Use
--sandbox read-onlyfor review, diagnosis, or planning tasks. - Avoid
--dangerously-bypass-approvals-and-sandbox/--yolounless the user explicitly asks for an unsafe fully trusted run. - Do not install Codex automatically unless the user asked you to. If missing, fall back to Claude Code or work directly.
Selection Policy
Prefer Codex first for coding work. Before invoking it, run a quick availability check:
if command -v codex >/dev/null 2>&1; then
codex --version
codex login status >/dev/null 2>&1
elif command -v claude >/dev/null 2>&1; then
echo "Codex is unavailable; use the claude-code skill instead."
else
echo "Neither codex nor claude is installed; continue directly or ask the user to install one."
fi
Interpret the result:
codexmissing: use theclaude-codeskill ifclaudeis installed, otherwise solve with available tools or ask the user to install Codex.codex login statusfails: tell the user to runcodex login(or configure their API key) and use Claude Code if available.- Both CLIs available: keep Codex as the default unless the user specifically asked for Claude Code.
Preflight Checklist
Before delegating:
- Identify the project root:
git rev-parse --show-toplevel 2>/dev/null || pwd. - Check the current diff with
git status --shortso user-owned changes are visible. - Convert the user's request into a concise task prompt with success criteria, files or areas to inspect, constraints, and expected verification commands.
- Decide sandbox mode:
workspace-writefor edits,read-onlyfor reviews. - Decide whether the task is small enough to do directly. Use Codex for broad, multi-file, uncertain, or test-heavy coding work.
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.
- 2d ago First seen · 163 lines · 95 tokens per session scan A 395384376c8a
codex is a skill published in the GitHub repository ldclabs/anda-bot (23 stars, last pushed 24d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,745 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…