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.
git clone --depth 1 https://github.com/2aronS/Duel-AgentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/2arons/duel-agents/setup)<a href="https://agentmods.dev/commands/2arons/duel-agents/setup"><img src="https://agentmods.dev/badge/commands/2arons/duel-agents/setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/2arons/duel-agents/setup"><img src="https://agentmods.dev/badge/commands/2arons/duel-agents/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00168 |
| Opus 5.5 | $0.00004 | $0.00067 |
| Sonnet 5.5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
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 1mo 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.
What it actually says
Duel Agents setup
Walk the user through Duel Agents setup:
- Confirm they have a Duel API key from https://duelagents.com/dashboard/settings
- Run
npx @duel-agents/install claude-codeor configure~/.claude/.env:ANTHROPIC_BASE_URL=https://duelagents.com/v1ANTHROPIC_API_KEY=<their duel_* key>
- Run
npx @duel-agents/install doctorto verify connectivity - 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.
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.
- 1mo ago First seen · 17 lines · 10 tokens per session scan A aa955981b172
setup is a command published in the GitHub repository 2aronS/Duel-Agents (745 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 168 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
apply
Replay a saved recipe through provider setup and optional wiring; inspect partial results. Usage — /stack:apply.
recommend
Recommend providers for a goal and save the result as a reusable recipe. Usage — /stack:recommend.
add
Provision a service and wire its secrets + MCP entry. Usage — /stack:add.
doctor
Inspect available provider checks and report failed or unchecked services.
status
Show a one-screen overview of the current stack.
list
List services configured in this stack.