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 skills/valpere/chorus/votenpx skills add valpere/chorus --skill votegit clone --depth 1 https://github.com/valpere/chorusWrote 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/skills/valpere/chorus/vote)<a href="https://agentmods.dev/skills/valpere/chorus/vote"><img src="https://agentmods.dev/badge/skills/valpere/chorus/vote.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.00714 |
| Opus 5 | $0.00016 | $0.00357 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
chorus-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chorus: Parallel Vote
When to use
- User wants a decision signal: "should we adopt X?", "vote on whether we should Y"
- User says "vote", "take a vote", "poll the agents", or "yes/no from all agents"
- You want a quick consensus check before committing to an approach
- Use the council skill instead when you want reasoning and trade-offs
Your role
You are the SCOPE voter. Your vote should reflect whether the proposition is the smallest viable solution or introduces unnecessary complexity. Vote YES if the scope is appropriate, NO if it seems over-engineered or under-specified, ABSTAIN if context is insufficient.
Invocation
Spawn four agents in parallel, then cast your own vote:
# Step 1: spawn four agents in parallel
claude --print "Vote on the following proposition. Reply with a single line starting with YES, NO, or ABSTAIN (uppercase), followed by one sentence of rationale. No other text.\n\nProposition: <proposition>" --dangerously-skip-permissions &
CLAUDE_PID=$!
gemini --prompt "Vote on the following proposition. Reply with a single line starting with YES, NO, or ABSTAIN (uppercase), followed by one sentence of rationale. No other text.\n\nProposition: <proposition>" --yolo --output-format text &
GEMINI_PID=$!
agent -p --force "Vote on the following proposition. Reply with a single line starting with YES, NO, or ABSTAIN (uppercase), followed by one sentence of rationale. No other text.\n\nProposition: <proposition>" &
CURSOR_PID=$!
kilo run --auto "Vote on the following proposition. Reply with a single line starting with YES, NO, or ABSTAIN (uppercase), followed by one sentence of rationale. No other text.\n\nProposition: <proposition>" &
KILO_PID=$!
# Step 2: wait for all
wait $CLAUDE_PID $GEMINI_PID $CURSOR_PID $KILO_PID
Graceful degradation: Check each agent with command -v <binary> before spawning. Skip missing agents and warn the user. Proceed as long as at least 2 agents (including yourself) are available.
Casting your vote
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.
- 5d ago First seen · 80 lines · 32 tokens per session scan A ffc12786738e
chorus-vote is a skill published in the GitHub repository valpere/chorus (10 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 714 once invoked, about $0.0002 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 skills, from other repositories
issue-maintenance
Periodic and on-demand maintenance pass over a repo's open GitHub issue backlog. Re-labels miscategorized or unlabeled issues (bug/enhancement/question/invalid/duplicate) and bug lifecycle labels (needs-repro/needs-info) following the same decision logic as Anthropic's own dogfooded triage-issue command; re-scores…
evidence-check
An honesty gate that makes an AI back up its claims with real evidence instead of presenting guesses as fact. Use as an always-on background behavior, and invoke explicitly when the user says show your work, prove it, how do you know that, evidence check, what's your source, back that up, or when the AI is…
engram-rebuild
이미 설치된 engram 환경에 개발 변경을 적용한다. dev-rebuild.ps1 로 충분한지 INSTALL.ps1 전체를 돌려야 하는지 판단하고 실행한다. 트리거 — 재빌드, 리빌드, dev 변경 적용, 설치본에 반영, overlay 재시작, exe 갱신, "고친 거 확인하려면 뭐 돌려야 해", rebuild, redeploy.
ci-fix-with-memory
Automatically invoke when CI checks fail on a PR. Triggers on: any mention of CI failure, red checks, failed GitHub Actions, or "CI is broken/failing". Reads session handoffs and a known-issues log to avoid repeating failed fix attempts. Do NOT wait for user to ask — invoke as soon as a CI failure is confirmed. Not…
comment-reaper
Finds and removes unnecessary code comments - the ones that restate the code, cite an issue number, narrate refactor history, or wrap a one-line function in six lines of JSDoc. Sorts every find into auto-fix, propose, or never-touch, so the WHY comments survive the sweep. Trigger on: "comment reaper", "reap comments"…
plain-language-audit
Sweeps a codebase's text — comments, docstrings, markdown docs, and user-facing UI copy — for jargon that could be plainer, AI writing tells/tropes, and verbose text that could be tightened. Auto-fixes unambiguous swaps, surfaces judgment calls for review. Trigger on: "jargon audit", "plain language audit", "find…