{"skill_id":"codex","version":"1.1.9","sha256":"59692b3ea4e3e06068689a25a0fc1f431826547728926f7f3941e78a747fff15","required_env_vars":["ARGUS_BASE_URL"],"detail_url":"https://api.argusfa.com/v1/skills/codex","download_url":"https://api.argusfa.com/v1/skills/codex/download","content":"---\nname: argus\ndescription: Retrieve machine-readable, source-backed facts and neutral metadata from Argus.\n---\n\n# Argus Data Layer\n\n## Customer-Side Installation\n\nSet `ARGUS_BASE_URL`, run `argus auth login`, and use the live Agent Tool Registry as the runtime authority. Approved unattended clients may read `ARGUS_MACHINE_API_KEY`; do not pass credentials through a remote shell.\n\nAuthentication uses `argus auth login` or an approved machine credential. Discover the live contract with `tool:agent_tool_registry` and field definitions with `tool:field_catalog`; permissions and license metadata remain enforced and auditable.\n\nUse the smallest read-only tool, such as `tool:company_master`, `tool:filing_search`, `tool:filing_evidence_extract`, `tool:event_timeline`, `tool:market_data_snapshot`, or `tool:point_in_time_dataset_export`. Supply request `as_of` when reproducibility matters; validate returned `effective_as_of` as response metadata.\n\nRun `argus tool-registry`, then apply each binding's `parameter_aliases` and `parameter_encodings`. CLI and MCP list arguments use comma-separated strings; REST lists use JSON arrays. For REST use live `/openapi.json`; for MCP use `list_tools().inputSchema`. Business calls return `success`/`result`/`audit_id`, not the canonical contract-kernel envelope. Registry discovery returns a raw snapshot. With OAuth omit caller and institution identity fields; the server supplies them. Check MCP `isError` before decoding `structuredContent` or JSON text. Do not assume that example subjects exist in the production dataset; resolve real identifiers first and honor coded coverage gaps.\n\nArgus returns structured facts, evidence, quality, permissions, license, and audit metadata. It does not answer questions, write narratives, recommend actions, manage user state, execute strategies, or place orders. Missing data remains coded as partial, empty, or unavailable.\n\n## OAuth tool grants\n\nDiscovery does not grant execution rights. The signed `argus:tools:public` scope covers all 52 governed public business tools, including `metric_catalog` and the five bounded `stream_*` tools. Required signed scopes, permission, tenant, source-license, and output-policy checks still apply. Connector synchronization and platform administration are excluded. Do not retry a permission denial unchanged.\n","api_base_url":"https://api.argusfa.com","mcp_url":"https://mcp.argusfa.com/mcp"}