setup

A setup tool for connecting Claude Code with Codex, including configuration, sign-in checks, repair, and verification.

In plain words
What is it for?
Use it to check, configure, or repair the Claude Code–Codex connection. It reports planned changes before approved setup actions run.
Why use it?
It guides the bridge setup through defined stages and separates safe checks from changes that need approval. This helps avoid unclear arguments, missing Python requirements, and unsafe workspace selection.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/borda/ai-rig/setup
Any agent
npx skills add Borda/AI-Rig --skill setup
Clone the repo
git clone --depth 1 https://github.com/Borda/AI-Rig

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.01004
Opus 5 $0.00015 $0.00502
Sonnet 5 $0.00006 $0.00201
Haiku 4.5 $0.00003 $0.00100

Measured 2d ago against content hash 0eb425261e55, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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.

plugins/bridge_cc-codex/claude-skills/setup/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set Up the Bridge

Bootstrap and plan

  • Treat a plain invocation as action=all target=peer scope=auto live=prompt.
  • The loaded Claude plugin, Claude trust, Claude authentication, and current session are external bootstrap prerequisites. Never try to replace or restart the current invocation surface.
  • Reject a model-supplied workspace; use Claude's launch workspace.
  • Run python --version first and stop if it is unavailable or older than Python 3.10.
  • Parse only the documented key=value grammar plus the one-release compatibility forms --live and --direction codex|claude; reject ambiguous or unknown arguments.

For one resolved target, invoke:

python "${CLAUDE_PLUGIN_ROOT}/bin/bridge_setup.py" --current-host claude --workspace "<launch-workspace>" --action "<action>" --target "<target>" --scope "<scope>" --live "<live>"

The deterministic planner performs credential-free inspection and returns the setup result JSON defined by schemas/setup-result.schema.json.

Check and approved changes

For check, report the result and stop. For all, configure, or repair:

  1. Show every planned operations entry and the approval digest before any mutation.
  2. Obtain explicit approval for exactly that digest. State:
    • action and purpose;
    • exact native argv and resolved target/scope;
    • external capability;
    • credential behavior;
    • filesystem and host-configuration effects;
    • rollback evidence;
    • retry policy; and
    • safe denial outcome.
  3. After approval, rerun the identical command with --approve "<approval_digest>".

The host-held HMAC makes the digest tamper-evident but does not grant consent; explicit operator or host approval remains required. The digest is action-bound, expires, and is consumed by its first execution attempt. Never substitute --approve without its digest. A denial, changed or expired digest, replay, unsupported capability, failed probe, or failed native operation stops without retry.

Authentication

Read the full file on GitHub · 74 lines

Changes

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.

  1. 2d ago First seen · 74 lines · 30 tokens per session scan A 0eb425261e55

Subscribe to this mod's changes

setup is a skill published in the GitHub repository Borda/AI-Rig (25 stars, last pushed 9d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,004 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

apm-usage

Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any apm CLI command.

microsoft/apm · 49 tokens

clean-user-facing-text

Audit and finalize authorized natural-language text meant for readers: strip suspicious invisible Unicode, then rewrite prose while keeping facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product copy, UI…

ShadowAqueduct/watermark-remover · 121 tokens

sessions

Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior…

slopus/happy · 78 tokens

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens

daily-budget-check

Run a daily spend check-in against a daily budget on the Agent Monitor dashboard — today's spend vs the daily target, pace through the day, and the projected overage if the current pace holds. Uses /api/pricing/cost and /api/sessions (grouped by startedat = today). Use for a quick daily spend check-in or a…

hoangsonww/Claude-Code-Agent-Monitor · 81 tokens

ship-feature

Implement a feature safely end-to-end in this repository. Use when adding or changing functionality across backend, frontend, or MCP with required verification and documentation updates.

hoangsonww/Claude-Code-Agent-Monitor · 34 tokens