Chorus is a coordination harness for teams of coding agents and humans, combining agent orchestration, task tracking, permissions, observability, and recovery in one workflow. It is for collaborative software development where agents propose changes and people verify them before delivery, and the catalogue entries provide its skills, hooks, agents, commands, MCP integration, plugin, and configuration.
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/Chorus-AIDLC/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/chorus-aidlc/chorus/chorus-plugin)<a href="https://agentmods.dev/plugins/chorus-aidlc/chorus/chorus-plugin"><img src="https://agentmods.dev/badge/plugins/chorus-aidlc/chorus/chorus-plugin/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/chorus-aidlc/chorus/chorus-plugin"><img src="https://agentmods.dev/badge/plugins/chorus-aidlc/chorus/chorus-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chorus 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 yesterday.
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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What it installs
The manifest is a name and a version. 9 hooks, 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
- Hook TeammateIdle A not measured
- Hook SessionEnd A not measured
- Hook SubagentStart A not measured
- Hook SubagentStop A not measured
- Hook TaskCompleted A not measured
- Hook UserPromptSubmit A not measured
- MCP server chorus A not measured
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.
- yesterday Changed 5c8fb600a593
- 7d ago Changed 9cd7b97f4289
- 9d ago Changed 5ec249ae8c36
- 12d ago Changed ffdf017d8686
- 13d ago Changed 8f09919cce45
- 16d ago Changed aaa632521a62
- 18d ago Changed 2a463676ae03
- 23d ago Changed 5dfbe3686455
- 29d ago Changed 688cb574f847
- 1mo ago First seen · 65 lines scan A 106bc9400ccb
chorus is a plugin published in the GitHub repository Chorus-AIDLC/Chorus (1,202 stars, last pushed today), licensed AGPL-3.0. 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-30.
Other plugins, from other repositories
overclick
Claim, execute, and deliver cards on your own self-hosted OverClick board. Ships the workflow skill, the /overclick: commands, and hooks: a session-start board snapshot and a delivery commit check run by default, while the claim guard and the stop/harness guards ship disabled. The only network endpoint is the OverClic.
flux
Generate epics and tasks in Flux from project requirements. Ship with less chaos.
agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows. Plus two opt-in hooks: leg-guard…
agent-taskgraph
Build native Claude Code Agent Teams with goals, roles, task graphs, collaboration protocols, and lifecycles.
fizzy
Operate a self-hosted Fizzy kanban board via fizzy-cli. Use when creating cards or migrating Jira issues to Fizzy.
orchestrate
Decompose a large goal into a tree of parallel workers running in isolated git worktrees, collect typed handoffs, replan, repeat until terminal. Idiomatic Claude Code realization of Cursor /orchestrate.