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.
npx agentmods add commands/valpere/chorus/votegit clone --depth 1 https://github.com/valpere/chorusWhat 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 | $0.00020 | $0.00568 |
| Opus 5 | $0.00010 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
vote 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 3d 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
Put a yes/no proposition to five agents in parallel and return a tally.
Raw slash-command arguments:
$ARGUMENTS
Use when you want a decision signal, not synthesis. The tally reveals whether there is consensus. Use /chorus:council when you want reasoning and trade-offs instead.
Vote semantics:
- Each agent replies
YES,NO, orABSTAINfollowed by one sentence of rationale. - Output: a tally table (
| Vote | Count |) and a per-agent rationale section. - Verdict is determined by the caller — no chairman synthesis.
Agent roles (same as council):
- Claude — correctness and security lens
- Gemini — edge-case and risk lens
- Codex — scope and simplicity lens
- Cursor — codebase integration lens
- Kilo — maintainability lens
Execution mode:
- Default: foreground (tally needs immediate results).
- If
--backgroundis in the arguments, run in background mode. - If
--jsonis in the arguments, the companion emits{"command":"vote","tally":{"yes":N,"no":N,"abstain":N,"invalid":N},"results":[{name,vote,rationale,output,error,exitCode}]}on stdout. Warnings still go to stderr. - Strip
--background,--wait, and--jsonbefore passing to the companion.
Pre-flight: The companion automatically checks which agents are installed. Missing agents are reported in stderr. Voting proceeds with whatever agents are available — at least 2 are required; if fewer are installed the companion exits non-zero and you should tell the user to install more agents.
Foreground execution:
node "$CLAUDE_PLUGIN_ROOT/scripts/companion.mjs" vote $ARGUMENTS
Background execution:
Bash({
command: `node "$CLAUDE_PLUGIN_ROOT/scripts/companion.mjs" vote $ARGUMENTS`,
description: "Parallel vote",
run_in_background: true
})
Tell the user: "Vote started in the background. You'll be notified when it completes."
After the companion exits:
Return the tally and per-agent rationale verbatim. Do not adjudicate the result — the caller decides what the tally means. If the user asks "what does this mean?", you may interpret it, but the raw output should be shown first.
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.
- 3d ago First seen · 55 lines · 20 tokens per session scan A ea5ab9eba937
vote is a command published in the GitHub repository valpere/chorus (10 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 568 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-31.
Other commands, from other repositories
update-ai-versions
Look up the latest published versions of the AI coding assistants pinned in the Dockerfile and update the ARG lines in place.
yapper-help
The /yapper-help command displays full documentation for the Yapper plugin, including all modes, commands, behaviours, configuration options, and usage examples. This command is itself rendered in Professor mode by default, because a help document that is not thoroughly elaborated would be somewhat contrary to the…
yapper-review
The /yapper-review command performs a thorough, multi-line pull request review. Rather than posting terse inline comments like "this is wrong" or "use X instead," yapper-review produces fully-explained feedback that describes the issue, the reasoning behind the concern, the potential impact, and a concrete suggested…
yapper-commit
The /yapper-commit command generates a verbose, fully-explained Git commit message for the current change or a described change. The resulting commit message explains not just what changed, but why it changed, what problem it solves, and how the solution works — providing maximum context for future readers of the git…
yapper
The /yapper command activates the Yapper verbosity system. Once active, all subsequent responses in the session will be substantially expanded, elaborated, and enriched with definitions, transitions, and restatements.
mem-last
Prints latest memory cards for the current project.