New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Chorus CLI

by Chorus-AIDLC in Chorus-AIDLC/Chorus

How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp.

AGPL-3.0Auto-check: notesAgent Workflows

Install Chorus CLI

skills CLI
$ npx skills add Chorus-AIDLC/Chorus --skill chorus-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Chorus-AIDLC/Chorus chorus-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/chorus-hermes/chorus/skills/chorus-cli .claude/skills/chorus-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chorus-cli
GitHub stars
1.2k
Token cost
~1.2k tokens
SKILL.md length
563 words
Files
1
Skills in repo
64
Repo updated
First seen
Licence
AGPL-3.0

At a glance

How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp.

  • Works in 4 steps: Install → Configure agents — chorus agents → Connection environment variables → …
  • Tasks that involve Secrets management
  • SKILL.md covers 1. Install, 2. Configure agents — chorus…, 3. Connection environment… and 4. MCP operations — chorus mcp
  • Calls npm; needs CHORUS_API_KEY

What it does

Chorus CLI is an agent skill from Chorus-AIDLC/Chorus. How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp. A concise shared reference for any Hermes flow that drives Chorus from the shell (via terminal).

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Secrets management and MCP servers. It works with Model Context Protocol. The repository describes itself as: The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven Development Lifecycle). The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Secrets management
  • Tasks that involve MCP servers

Example prompts

  • “/chorus-cli”

Requirements

  • Node.js
  • A credential in CHORUS_API_KEY

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Install
  2. Configure agents — chorus agents
  3. Connection environment variables
  4. MCP operations — chorus mcp

What it can do on your machine

Read from SKILL.md and the folder at commit 4754822. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CHORUS_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chorus CLI loads about 1.2k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 563 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:56
    PI_KEY` in the environment or `~/.hermes/.env`.
  • NoteMentions a .env fileSKILL.md:66
    _KEY` from the environment or `~/.hermes/.env`.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Chorus-AIDLC/Chorus at commit 4754822, republished under its AGPL-3.0 licence (© Chorus-AIDLC). 563 words, ~1,240 tokens.

Download SKILL.mdSave it as .claude/skills/chorus-cli/SKILL.md (or your agent's skills folder).
name
chorus-cli
description
How to install, configure, and use the `chorus` CLI — install it, manage agents with `chorus agents` (add/remove/list), the connection environment variables, and MCP operations via `chorus mcp`. A concise shared reference for any Hermes flow that drives Chorus from the shell (via `terminal`).
license
AGPL-3.0
metadata.author
chorus
metadata.version
0.22.0
metadata.category
project-management
metadata.mcp_server
chorus

chorus-cli — using the chorus CLI

chorus (published as @chorus-aidlc/chorus) is the one command that configures this machine's coding agents for Chorus and talks to the Chorus MCP endpoint from the shell. This is a concise reference — run chorus --help and chorus <command> --help for the full flag surface. On Hermes, run these commands with the terminal tool.

1. Install

bash
npm install -g @chorus-aidlc/chorus       # unpinned — always installs the latest
chorus --version                          # must be >= 0.17.0 (provides `chorus agents` + `chorus mcp`)

2. Configure agents — chorus agents

Agent configuration lives in ~/.chorus/daemon.json; chorus agents is the CRUD group:

  • chorus agents (or chorus agents list) — list configured agents (name, UUID, backend). The API key is never printed; the agent named by CHORUS_AGENT_PROFILE is marked.

  • chorus agents add [--agents <ids>] [--all] [--url <u>] [--api-key <cho_…>] [--yes] [--dsh-profile <name>] — detect installed coding agents, install each one's Chorus plugin, and seed credentials (this is the former chorus init). Idempotent; safe to re-run. --help lists every flag. For Hermes, chorus agents add --agents hermes resolves the release tag to its commit SHA, installs both Hermes plugin directories (chorus and chorus-mcp) pinned to it with hermes plugins install … --ref <sha> --enable, and — when CHORUS_URL is not the loopback default — writes the native mcp_servers.chorus entry into $HERMES_HOME/config.yaml (literal <CHORUS_URL>/api/mcp URL, header kept as the Bearer ${CHORUS_API_KEY} placeholder). A Hermes agent is stored as offline: its presence and wakes come from the plugin's own hermes gateway connection, not the Chorus daemon.

  • chorus agents remove <name|uuid> — remove a configured agent from ~/.chorus/daemon.json (matched by UUID or name; an ambiguous name → use the UUID).

  • chorus agents run --name <name|uuid> [--type <type>] [--] [agent args…] — launch a configured agent's binary in the FOREGROUND with its Chorus connection injected into the child only (CHORUS_URL / CHORUS_API_KEY / CHORUS_AGENT_PROFILE; nothing is exported to the parent shell, and the key is never printed). Agent selection: single agent by default; else --name, else CHORUS_AGENT_PROFILE; ambiguous/none → error. Backend defaults to the agent's stored agentType, overridable with --type. Everything after -- is passed to the agent verbatim (never inspected). Type → binary: claude-code/claude→claude, codex→codex, kiro→kiro-cli, pi→pi, opencode→opencode, openclaw→openclaw, dsh→dsh. Agents added as opencode/openclaw/dsh are stored as offline → pass --type explicitly to launch them. For Hermes, check chorus agents run --help for a hermes type; otherwise start it directly with hermes (interactive) or hermes gateway (stay online for Chorus wakes), with CHORUS_URL / CHORUS_API_KEY in the environment or ~/.hermes/.env.

Show full SKILL.md (191 more words)Show less

3. Connection environment variables

  • CHORUS_URL — the Chorus instance URL.
  • CHORUS_API_KEY — an agent API key (cho_…).
  • CHORUS_AGENT_PROFILE — optional name or UUID of the agent to act as. When set, chorus mcp resolves that agent's key from ~/.chorus/daemon.json, so you need not export CHORUS_API_KEY for the CLI path. Daemon-woken sessions receive it automatically. The Chorus Hermes plugin itself does not read it: the plugin and its MCP entry use CHORUS_URL + CHORUS_API_KEY from the environment or ~/.hermes/.env.

4. MCP operations — chorus mcp

Call any Chorus MCP tool from the shell — a byte-exact, token-free path for large content:

  • chorus mcp call <tool> ['<json>'] [--arg-file key=<file>] [--agent <name|uuid>] — call a tool. --arg-file content=<file> streams a file's raw bytes into the JSON content string (no re-typing through the model). Identity resolves from --agent → CHORUS_AGENT_PROFILE → CHORUS_URL+CHORUS_API_KEY → a single configured agent.
  • chorus mcp whoami — print this agent's own UUID.
  • chorus mcp list — list the tools this agent may call.

Requires chorus >= 0.17.0 (the chorus mcp subcommand). See chorus mcp --help.

When chorus is not on PATH, Hermes has no bundled shell wrapper: call the native MCP tool directly (e.g. mcp__chorus__chorus_pm_add_document_draft) with the content read from the file via read_file.

© Chorus-AIDLC, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/chorus-hermes/chorus/skills/chorus-cli of Chorus-AIDLC/Chorus.

Open the folder on GitHubat commit 4754822

Compare with similar skills

Chorus CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chorus CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chorus CLI this skillChorus-AIDLC/Chorus1.2k—~1.2kAutomated safety check: NotesAGPL-3.0
Warp GUI to Agent CLI Migrationwarpdotdev/warp65k1 repos~2.1kAutomated safety check: PassAGPL-3.0
Flow Contextflowexec/flow137—~654Automated safety check: PassApache-2.0
Add Integrationindranilbanerjee/digital-marketing-pro8541 repos~1.8kAutomated safety check: NotesMIT
Auto Review Loop LLMAI4Scientist/nano-scientist1284 repos~1.8kAutomated safety check: WarnNone
MCP Security Auditboshi-xixixi/TraeSkill274—~2.2kAutomated safety check: PassMIT

Similar skills

  • Warp GUI to Agent CLI Migration

    warpdotdev/warp

    Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

  • Flow Context

    flowexec/flow

    This project uses flow for automation. An agent skill from flowexec/flow.

    137 GitHub stars~654 tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed

  • Add Integration

    indranilbanerjee/digital-marketing-pro

    Walk through adding a custom MCP server integration to the plugin — searches npm for an existing MCP package (or scaffolds a custom server from the plugin's guide), generates the exact .mcp.json…

    854 GitHub starsUsed in 1 repo~1.8k tokens
    Agent WorkflowsAuto-check: notes

  • Auto Review Loop LLM

    AI4Scientist/nano-scientist

    Autonomous research review loop using any OpenAI-compatible LLM API.

    128 GitHub starsUsed in 4 repos~1.8k tokens
    Agent WorkflowsAuto-check: warnings

  • MCP Security Audit

    boshi-xixixi/TraeSkill

    Audit MCP (Model Context Protocol) server configurations for security issues.

    274 GitHub stars~2.2k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed

  • Codex Agent Provider for NanoClaw

    nanocoai/nanoclaw

    Installs Codex as an agent provider for NanoClaw groups, with streaming, MCP tools, server-side history and vault-only credentials, next to or instead of Claude.

    31k GitHub stars~2.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check: notes

More from Chorus-AIDLC/Chorus

All 64 skills in this repo

  • E2E Verification

    Chorus-AIDLC/Chorus

    A skill your agent uses when manually verifying a Chorus frontend change in a real browser — finding local login credentials, driving the running dev server with the Playwright MCP, logging in…

    1.2k GitHub stars~1.5k tokensUpdated today
    Auto-check: notes

  • Blog

    Chorus-AIDLC/Chorus

    Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

    1.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Brainstorm

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas on Hermes.

    1.2k GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Brainstorm

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas.

    1.2k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Brainstorm Chorus

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas.

    1.2k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Chorus Brainstorm

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas.

    1.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Chorus CLI

What does Chorus CLI do?

How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp. Chorus CLI is an agent skill from Chorus-AIDLC/Chorus. How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp.

When should I use Chorus CLI?

Chorus CLI fits situations like: tasks that involve Secrets management; tasks that involve MCP servers.

How do I install Chorus CLI in Claude Code?

Run `npx skills add Chorus-AIDLC/Chorus --skill chorus-cli -a claude-code`. Or copy the skill folder (packages/chorus-hermes/chorus/skills/chorus-cli in Chorus-AIDLC/Chorus) into .claude/skills/chorus-cli in your project. Claude Code loads it when a task matches its description.

How do I install Chorus CLI in Codex?

Run `npx skills add Chorus-AIDLC/Chorus --skill chorus-cli -a codex`. Or copy the skill folder (packages/chorus-hermes/chorus/skills/chorus-cli in Chorus-AIDLC/Chorus) into .agents/skills/chorus-cli in your project. Codex loads it when a task matches its description.

Can I use Chorus CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Chorus-AIDLC/Chorus --skill chorus-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chorus-cli, .gemini/skills/chorus-cli, .github/skills/chorus-cli and .opencode/skills/chorus-cli in your project.

What does Chorus CLI need to run?

Going by SKILL.md and its folder, Chorus CLI needs the command-line tools its instructions call (npm) and credentials named CHORUS_API_KEY. Our summary lists: Node.js; A credential in CHORUS_API_KEY.

Does Chorus CLI access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Chorus CLI safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Chorus CLI use?

Chorus CLI is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chorus CLI use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chorus CLI?

Skills that share tags, products or a category with Chorus CLI: Warp GUI to Agent CLI Migration (warpdotdev/warp, 65k stars), Flow Context (flowexec/flow, 137 stars), Add Integration (indranilbanerjee/digital-marketing-pro, 854 stars) and Auto Review Loop LLM (AI4Scientist/nano-scientist, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chorus CLI?

Chorus-AIDLC (a GitHub organization) maintains it in Chorus-AIDLC/Chorus, which has 1,192 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 7, 2026.

Source: Chorus-AIDLC/Chorus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.