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/plugins/valpere/chorus/claude)<a href="https://agentmods.dev/plugins/valpere/chorus/claude"><img src="https://agentmods.dev/badge/plugins/valpere/chorus/claude/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/plugins/valpere/chorus/claude"><img src="https://agentmods.dev/badge/plugins/valpere/chorus/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude 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
{
"name": "claude",
"version": "1.0.0",
"description": "Delegate tasks and code reviews to a second Claude Code instance.",
"author": { "name": "valpere" }
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 20 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 7 lines scan A 2f50941a6deb
claude is a plugin published in the GitHub repository valpere/chorus (10 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
workflow-skills
Issue triage, TDD, CI fix-with-memory, design-system guard, PR review, dead-code and doc-rot cleanup, comment and test reaping, code-health and visual-QA audits, evidence-checked claims, worktree setup, project bootstrap, cross-provider skill parity, and session wrap-up skills.
code-refactoring
Code cleanup, refactoring automation, and technical debt management with context restoration.
comprehensive-review
Multi-perspective code analysis covering architecture, security, and best practices.
codex
Use Codex from Claude Code to review code or delegate tasks. Community fork by zebbern.
rigorous-paper-reviewer
Deep 7-pass technical review of LaTeX papers — structure, notation, theorem/proof, numerics, complexity, figures, coherence. Includes a static Python verifier for automated triage of labels, cross-references, and structure.
unslop
Review and revise writing, code and websites that read as generic AI output. Three scanners for prose, source code and web design, guidance for what a scanner can't see, and a method for building a voice profile from your own writing.