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/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/rules/valpere/chorus/rule)<a href="https://agentmods.dev/rules/valpere/chorus/rule"><img src="https://agentmods.dev/badge/rules/valpere/chorus/rule/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/rules/valpere/chorus/rule"><img src="https://agentmods.dev/badge/rules/valpere/chorus/rule.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.00037 | $0.00187 |
| Opus 5.5 | $0.00015 | $0.00075 |
| Sonnet 5.5 | $0.00007 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
RULE 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
Chorus: Delegate to Claude
When to use
- User explicitly asks to delegate to Claude
- User wants a second opinion from Claude
- User wants to compare your answer with Claude's
- User asks "what would Claude say?" or similar
Invocation
Run Claude Code non-interactively:
claude --print "<task>" --dangerously-skip-permissions
The --print flag runs Claude in non-interactive mode.
The --dangerously-skip-permissions flag is required for automated execution.
Output handling
Return Claude's output verbatim — no paraphrasing, no summaries, no added commentary.
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 · 30 lines · 37 tokens per session scan A 674c76a7820f
RULE is a cursor rule published in the GitHub repository valpere/chorus (10 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 187 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
mandatory
Mandatory rules for all work in this repository — always applied.
frontend-pages
Rules for Next.js pages, BFF routes, and React components in apps/web.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.