setup

A setup command for connecting Claude Code to Duel Agents, a service that routes requests through its own API. It helps configure a Duel API key and check that the connection works.

In plain words
What is it for?
Use it to set up Duel Agents in Claude Code, verify the connection, or find the SDK for building custom tools.
Why use it?
It removes the need to edit connection settings by hand and helps catch key or connectivity problems. Duel API keys are required; direct Anthropic keys do not work with Duel.

Command

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 commands/2arons/duel-agents/setup
Clone the repo
git clone --depth 1 https://github.com/2aronS/Duel-Agents
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 168 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.00010 $0.00168
Opus 5 $0.00005 $0.00084
Sonnet 5 $0.00002 $0.00034
Haiku 4.5 $0.00001 $0.00017

Measured 2d ago against content hash aa955981b172, 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.

integrations/claude-plugin/commands/setup.md · 17 lines

What it actually says

Duel Agents setup

Walk the user through Duel Agents setup:

  1. Confirm they have a Duel API key from https://duelagents.com/dashboard/settings
  2. Run npx @duel-agents/install claude-code or configure ~/.claude/.env:
    • ANTHROPIC_BASE_URL=https://duelagents.com/v1
    • ANTHROPIC_API_KEY=<their duel_* key>
  3. Run npx @duel-agents/install doctor to verify connectivity
  4. Remind them: only Duel API keys work. Do not use raw Anthropic keys with Duel

If they want to build custom tooling, point them to @duel-agents/sdk.

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 · 17 lines · 10 tokens per session scan A aa955981b172

Subscribe to this mod's changes

setup is a command published in the GitHub repository 2aronS/Duel-Agents (774 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 168 once invoked, about $0.0001 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.