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 commands/arystos/skill-codex/codex-consultgit clone --depth 1 https://github.com/Arystos/skill-codexWhat 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.00000 | $0.00349 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
codex-consult 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.
What it actually says
Consult Codex for a Second Opinion
Get Codex's perspective on a technical question, plan, or approach.
Instructions
You are consulting Codex for a second opinion. This is read-only — no files will be modified.
-
Parse the question from
$ARGUMENTS. This could be:- A technical question about the codebase
- A plan you want validated before implementing
- An architecture decision you want a second perspective on
- A debugging hypothesis you want challenged
- A technology choice comparison
-
Prepare a focused prompt for Codex. Include:
- The specific question or plan to evaluate
- Relevant context: file paths, code snippets, constraints
- What kind of feedback you want (validation, alternatives, risks, tradeoffs)
-
Call the
codex_execMCP tool with:prompt: "Provide your analysis and recommendation on the following question. Consider tradeoffs, alternatives, and potential risks. Be specific and cite concrete examples where possible.\n\n"mode: "exec"
-
Synthesize both perspectives for the user:
- Present Codex's analysis
- Provide your own independent analysis
- Where you agree and why
- Where you disagree and why (with evidence)
- Your recommended path forward with reasoning
Important
- Codex runs in read-only mode — it cannot modify files
- This is a consultation, not a delegation — the final decision rationale comes from this conversation
- If you and Codex strongly disagree, present both arguments fairly and let the user decide
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 · 37 lines · 0 tokens per session scan A 48d9b677c246
codex-consult is a command published in the GitHub repository Arystos/skill-codex (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 349 tokens. 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-31.
Other commands, from other repositories
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
docs-review
Phase 4 of documenting-projects: Quality gate with 8 measurable criteria and iteration. Triggers: '/docs-review', invoked by documenting-projects orchestrator.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
test
Run all PandaFilter verification steps in order. Stop and report on first failure. This is the required pre-commit gate.