agents-docs

compatibility	Requires network access and a URL-capable web fetch or curl.
coordination	exempt
disable-model-invocation	false
name	agents-docs
user-invocable	true
description	Use for current official documentation about Codex, Codex CLI, or Claude Code behavior, configuration, prompting, skills, permissions, tools, surfaces, capabilities, troubleshooting, hooks, app-server, or hook trust; fetch the relevant official URL before answering.

Agents Docs

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

Supported Chat Hosts

Before doing any work, identify the current chat host. If it is not Claude Code or Codex CLI, stop with this error: This skill only works in Claude Code or Codex CLI.

Answer Codex and Claude Code product questions from the narrowest relevant live official documentation.

Classify the request

Classify the request as Codex, Claude Code, or a comparison. Activate only for questions about those products and their documented behavior. Do not capture unrelated repository mentions, generic agent development, provider APIs, SDKs, pricing, authentication, model selection, migration, or managed-agent workflows.

Route official sources

• For Codex, use only https://developers.openai.com. Start broad product research at https://developers.openai.com/codex/codex-manual.md.
• For Claude Code, use only https://code.claude.com. Start broad product research at https://code.claude.com/docs/en/overview.md.
• For a specific topic, run a compact domain-restricted web search for the exact official page, then fetch its Markdown representation when available. Retrieve only the page or section needed for the answer; never fetch a complete documentation inventory as a discovery shortcut.
• For broad Codex synthesis, fetch the consolidated manual to an operating-system temporary location, search it with rg, and read only the matching heading range into context. Do not write it or a cache into the repository or skill installation.
• Prefer the current client's URL-capable fetch. If it cannot fetch a known URL, use curl -fsSL.
• For comparisons, complete both provider routes independently. Never infer one product's behavior from the other's documentation.

Follow redirects only within the matching official domain and cite the final page URL.

Investigate under-documented Codex configuration

When a Codex feature or config.toml key is missing from the prose documentation, use this bounded procedure:

1. Record the installed client and effective feature state with codex --version and codex features list.
2. Fetch the official config-schema.json to an operating-system temporary location, then search only the relevant definition or path. Do not cache the schema in the repository or skill installation.
3. Compare the schema with the current prose config reference. Treat schema-only fields as under-documented, not as behavior guaranteed by every client.
4. Validate candidate syntax against the installed client with codex --strict-config --help; use one-off -c overrides when needed without persisting changes. Parsing acceptance is not runtime proof.
5. Report evidence separately as official docs/schema, local observations, or inference. If sources disagree, prefer the installed client's observed behavior for the user's environment and disclose the discrepancy.

Do not turn this into a full feature inventory: investigate only the key or feature relevant to the request.

Answer from evidence

• Treat live official documentation as authoritative for published product claims. Do not answer current or unstable product facts from memory when the relevant page can be fetched.
• Cite the exact official page supporting each material claim, not a broad entry point when a topic-specific page was used. Prefer short paraphrases; quote only when exact wording matters.
• If verified local commands, versions, configuration, or callable capabilities conflict with the latest docs, report the discrepancy and prefer the observed behavior for that installed environment.
• If an exact term is absent, search obvious adjacent official concepts and state that the term itself is not documented.

Route Codex hook, app-server, and trust questions

For Codex hooks, app-server, managed hooks, or hook-trust operations, first fetch the relevant official pages:

• https://developers.openai.com/codex/hooks
• https://developers.openai.com/codex/app-server

Then read the version-aware hooks reference. Use its local protocol and config details only when the installed client is explicitly verified as the version named there. Keep official behavior and local observations distinct in the answer; do not turn a local implementation detail into a product guarantee.

Bound failures

If retrieval fails, try the direct URL and one domain-restricted search, then stop expanding sources. State the bounded uncertainty. Use local --help, --version, configuration, or observed behavior only when relevant and label it as local evidence. Never silently substitute third-party sources, another provider's docs, or bundled knowledge.

For comparisons, answer a supported side even if the other provider is unavailable; mark the unsupported side unknown instead of manufacturing symmetry. In network-disabled sessions, fail transparently without creating repository files or persistent caches.

Completion

Finish when the answer uses the narrowest relevant official source, includes precise citations, and exposes any documentation/local-version discrepancy or retrieval limitation.