--- name: redgold description: Set up Redgold tools and reusable instructions for an existing Claude Code or Codex agent, using a Redgold API key for search and authorized remote builds. --- # Connect your agent to Redgold Public entrypoint: https://redgold.ai/skill.md. Read this when asked to connect an existing agent, install or update Redgold tools, or make that setup persistent. The documentation index is https://docs.redgold.ai/llms.txt. ## Install the tools Use the person's existing key through their secret manager as `REDGOLD_API_KEY`. If it is unavailable, ask them to configure it securely. Never ask them to paste it into the conversation, print it, or put it in a skill or repository. Keep the person's existing Claude/Codex model-provider settings. The public bootstrap is https://redgold.ai/install.sh. Download and inspect it, then run it with the key available to its process: ```sh curl -fsSL https://redgold.ai/install.sh -o redgold-install.sh bash redgold-install.sh --without-engine --without-aws export PATH="$HOME/.redgold/bin:$PATH" redgold --version rac --version rci --version ``` Use a disposable directory outside version control for the downloaded script. This installs the terminal client `redgold`, agent CLI `rac`, and CI companion `rci`. The local data engine and AWS CLI are optional; omit those exclusions only when the task needs them. The installer checks release hashes and signatures. It supports Linux x86_64 and macOS; the current Linux binaries need glibc 2.39 or newer. Inspect `--help` and report an unsupported platform instead of replacing a working installation with an incompatible binary. Add the bin directory to the person's shell PATH if needed, preserving their shell config. ## Install persistent skills Inspect `rac skills list` and `rac skills install --help`. Install `redgold`, `rac-research` and `rac-build` for the agent being configured: ```sh # Codex: user skills, available across repositories rac skills install redgold --target "$HOME/.agents/skills" rac skills install rac-research --target "$HOME/.agents/skills" rac skills install rac-build --target "$HOME/.agents/skills" # Claude Code: personal skills rac skills install redgold --target "$HOME/.claude/skills" rac skills install rac-research --target "$HOME/.claude/skills" rac skills install rac-build --target "$HOME/.claude/skills" ``` Choose the appropriate block; install both when the person uses both agents. Honor a custom skill location already used by their harness. Codex also supports repository `.agents/skills`; Claude Code supports repository `.claude/skills`. The CLI's default target can differ from these explicit paths in older releases. Skill location references: [Codex](https://developers.openai.com/codex/skills) and [Claude Code](https://code.claude.com/docs/en/skills). If a binary does not bundle a listed skill yet, fetch its public Markdown: - [redgold](https://redgold.ai/skills/redgold/SKILL.md) - [rac-research](https://redgold.ai/skills/rac-research/SKILL.md) - [rac-build](https://redgold.ai/skills/rac-build/SKILL.md) Review the downloaded text and save each as `//SKILL.md`. Preserve locally edited skills: compare changes before using `--overwrite`. Codex discovers skill changes automatically; restart it if they do not appear. Start a new Claude Code session if needed to discover newly installed skills. For a repository where ongoing Redgold use was requested, add or update a short note in its existing `AGENTS.md` or `CLAUDE.md`, preserving all other guidance: > Use the redgold, rac-research and rac-build skills for Redgold setup, web > research and authorized remote builds. Discover current syntax with scoped > `rac ... --help`. Keep credentials in the configured secret store. Use quoted > prices and the user's budget for paid work; use only the project's approved > build endpoint. Update tools and skills without overwriting local changes. ## Verify access `rac` sends search requests to the public API by default. Set `AC_SEARCH_API_BASE=https://api.redgold.ai` when an existing development override would otherwise select another installation. Use a key with web-search access; an installer/model key alone does not establish that permission or balance. First request a quote, which performs no provider work or purchase: ```sh rac search 'Rust official documentation' --mode enhanced --provider exa --max 3 --max-cost-usd 0.02 --quote ``` When free search is available for this account, verify one real request with `rac search 'Rust official documentation' --mode free --max 3 --json`. Inspect `provider_statuses`: a successful HTTP response does not establish useful results. Paid execution requires the person's budget; keep a stable `RAC_WEB_TOOL_REQUEST_ID` and the same arguments for retries. For builds, read [rac-build](https://redgold.ai/skills/rac-build/SKILL.md). Remote builds use `rac cargo` or `rac pnpm`; `rac ci` and `rac leg` delegate to the installed `rci` companion. An installed binary or search key does not provision a builder. Configure and verify the project's authorized build endpoint and credential before uploading code or submitting work. Report a missing endpoint or entitlement as setup still needed. Report the installed versions, skill locations, search result, and build-access result separately. A 401/403 means authentication or permission needs attention; a 402 means the account needs credit. Do not buy credit as part of setup. ## Updates and new accounts To update, inspect and rerun the same official bootstrap with the existing key, then compare and reinstall the selected skills. `rac skills show ` shows the instructions bundled with that release. Fetch this public entrypoint again when the installed release's setup differs. People without an account can start at https://redgold.ai/signup. Some installations expose `rac signup --free` for a limited search-only identity; check the selected service before offering it as an account setup route. x402 currently pays for individual search/fetch requests on the development service, using Base Sepolia test USDC. It does not create a Redgold login, API key, workspace, membership, or build entitlement. Mainnet x402 signup is not available. Discover the selected service's live `/.well-known/agent-services.json` before proposing a payment flow. Linking an elusivedb identity also needs verified control of both accounts; a matching username or a payment is insufficient.