setting-up-coral

setting-up-coral is a skill for Claude Code from Human-Agent-Society/CORAL. It costs 122 tokens per session (1,721 once invoked), scanned A, original, Apache-2.0.

A setup guide for CORAL, a tool that coordinates runs involving multiple coding agents.

In plain words
What is it for?
Use it to detect supported agent programs, create named bindings, check their login and model configuration, and connect them to CORAL tasks.
Why use it?
It records which agent programs and models are available on a computer, so project tasks can refer to a short name without storing machine-specific details in the project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Codex; mentions Cursor.

Part of the coral plugin — 4 skills, 2 agents, 1 hook shipped together

Good fit Use it to detect supported agent programs, create named bindings, check their login and model configuration, and connect them to CORAL tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/human-agent-society/coral/setting-up-coral
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.

Any agent
npx skills add Human-Agent-Society/CORAL --skill setting-up-coral
Clone the repo
git clone --depth 1 https://github.com/Human-Agent-Society/CORAL

Made for: Claude Code.

Or install coral, the plugin that ships this one along with the rest of its 4 skills, 2 agents, 1 hook.

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

agentmods badge for setting-up-coral

README.md
[![agentmods](https://agentmods.dev/badge/skills/human-agent-society/coral/setting-up-coral/github.svg)](https://agentmods.dev/skills/human-agent-society/coral/setting-up-coral)
Your own site
<a href="https://agentmods.dev/skills/human-agent-society/coral/setting-up-coral"><img src="https://agentmods.dev/badge/skills/human-agent-society/coral/setting-up-coral/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.

agentmods 80×15 button for setting-up-coral

Your own site · 80×15
<a href="https://agentmods.dev/skills/human-agent-society/coral/setting-up-coral"><img src="https://agentmods.dev/badge/skills/human-agent-society/coral/setting-up-coral.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,721 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00122 $0.01721
Opus 5 $0.00061 $0.00860
Sonnet 5 $0.00024 $0.00344
Haiku 4.5 $0.00012 $0.00172

Measured 12d ago against content hash 320c9a8b6909, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

setting-up-coral 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 12d 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.

plugin/skills/setting-up-coral/SKILL.md · 113 lines

How it starts

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

Setting up coral (agent bindings)

After installing the coral CLI, the one-time machine setup is registering which agent runtimes you have as named bindings. A binding bundles a runtime + CLI command + default model + runtime options under a short name, stored at:

~/.config/coral/agents.yaml        # honors $XDG_CONFIG_HOME; override with $CORAL_AGENTS_CONFIG

Tasks then reference a binding by name (agents.binding: claude-opus) instead of repeating runtime/model in every task.yaml. This keeps task.yaml portable (topology: how many agents, which roles) and machine-specific details (which CLIs are installed here) in a user-level file that's never committed.

Bindings store no credentials. Authentication stays with each runtime's native login (claude, codex, cursor-agent login, kiro-cli setup). coral setup only records runtime/command/model metadata. If a run fails to auth, fix it via the runtime's own login, not coral.

1. Detect + create bindings (the fast path)

coral setup

Scans PATH for every supported runtime (claude, codex, cursor-agent, opencode, kiro-cli, pi), prints a detection report (✓ = found), then offers a numbered wizard. For each pick it asks for a binding name, model, and an optional role-seed file. After each one it asks "Add another binding for X?" — say yes to make several bindings for the same runtime (e.g. claude-opus and claude-sonnet). The first binding created becomes the default.

  • coral setup --non-interactive — just print the detection report (CI / piping); creates nothing.

2. Create / update a single binding (scriptable)

For a custom command path, model, or runtime option — or for CI where you can't use the wizard:

coral setup agent --name claude-opus --runtime claude_code --model opus
coral setup agent --name codex-high  --runtime codex --option model_reasoning_effort=high
coral setup agent --name claude-opus --runtime claude_code --model opus --default   # make it the default

Read the full file on GitHub · 113 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. 12d ago First seen · 113 lines · 122 tokens per session scan A 320c9a8b6909

Subscribe to this mod's changes

setting-up-coral is a skill published in the GitHub repository Human-Agent-Society/CORAL (975 stars, last pushed 3d ago), licensed Apache-2.0. It adds 122 tokens to every session and 1,721 once invoked, about $0.0006 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.