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 skills add valpere/chorus --skill parallel-debuggit 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/parallel-debug)<a href="https://agentmods.dev/skills/valpere/chorus/parallel-debug"><img src="https://agentmods.dev/badge/skills/valpere/chorus/parallel-debug/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/skills/valpere/chorus/parallel-debug"><img src="https://agentmods.dev/badge/skills/valpere/chorus/parallel-debug.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.00044 | $0.00478 |
| Opus 5.5 | $0.00018 | $0.00191 |
| Sonnet 5.5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
chorus-parallel-debug 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: Parallel Debug
When to use
- Root cause of a bug is unclear
- User says "parallel debug", "chorus debug", "hypotheses from all agents"
Your role
You generate hypotheses focused on edge cases in input handling, type coercion, off-by-one errors.
Invocation
SYMPTOM="<symptom>"
claude --print "Root-cause hypotheses, ranked by likelihood (numbered list). Focus: application logic, state management.\n\nSymptom: $SYMPTOM" --dangerously-skip-permissions &
CLAUDE_PID=$!
gemini --prompt "Root-cause hypotheses, ranked by likelihood (numbered list). Focus: infrastructure, concurrency, environment.\n\nSymptom: $SYMPTOM" --yolo --output-format text &
GEMINI_PID=$!
agent -p --force "Root-cause hypotheses, ranked by likelihood (numbered list). Focus: framework, library, and third-party integration issues.\n\nSymptom: $SYMPTOM" &
CURSOR_PID=$!
kilo run --auto "Root-cause hypotheses, ranked by likelihood (numbered list). Focus: naming confusion, type misuse, readability issues that hide bugs.\n\nSymptom: $SYMPTOM" &
KILO_PID=$!
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.
Output handling
Merge all available hypothesis lists (up to four agents + your edge-case hypotheses), prioritize ones flagged by multiple agents:
## Hypothesis Pool (ranked)
1. … (Claude + Gemini)
2. … (Codex)
## Investigation Plan
1. Check X first — rules out hypotheses 1 and 3
Known limitation
Codex sandbox limits access to the current working directory.
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 · 55 lines · 44 tokens per session scan A c567293bb8ad
chorus-parallel-debug is a skill published in the GitHub repository valpere/chorus (10 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 478 once invoked, about $0.0002 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 skills, from other repositories
ci-fix-with-memory
Automatically invoke when CI checks fail on a PR. Do NOT wait for the user to ask; invoke as soon as a CI failure is confirmed. Reads session handoffs and a known-issues log so failed fixes aren't retried. Trigger on: "CI is failing", "red checks", "GitHub Actions failed", "fix CI".
test-fix
Automatically invoke when any test run produces failures: FAIL output, test errors, or assertion failures in unit or E2E suites. Do NOT wait for the user to ask. Hard limit of 3 fix attempts per failure, then stops and escalates. Trigger on: "tests are failing", "fix the tests", "tests are broken".
band-aid-finder
Finds fixes that hide a symptom instead of fixing the cause, traces each to its root cause, and proposes the real fix. Allows deliberate, documented mitigations. Trigger on: "is this a real fix or a band-aid", "am I treating the symptom", "why does this keep happening", "find the root cause".
browser-debugger-cli
Inspects live web pages through the Chrome DevTools Protocol with the bdg CLI: targeted DOM queries, computed styles, layout debugging, and raw CDP calls, without loading a full page snapshot. Trigger on: "inspect element", "check computed styles", "query the DOM", "debug layout".
tencentcloud-cls
Search and analyze Tencent Cloud CLS (Cloud Log Service) logs. Use whenever the user asks to: search logs, debug API errors, trace requests by trace ID, find 5xx errors, run CQL/SQL analytics over log topics, extract structured fields. Backed by the official tencentcloud-sdk-python CLS client.
chisle-audit
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in…