What is chamber-synthesizer?

A security-review coordinator that runs a debate between agents proposing, tracing, and defending vulnerability hypotheses. It weighs their evidence, decides the outcome, rates severity, and writes finding drafts.

It is for coordinating review chambers, checking probe results and known attack patterns, resolving disputes, and drafting confirmed vulnerability findings.

It gives competing security arguments a defined review process and keeps one role responsible for the final decision and written result.

chamber-synthesizer — Agent for Claude Code by vigolium

Install

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.

Clone the repo

git clone --depth 1 https://github.com/vigolium/piolium

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/vigolium/piolium/chamber-synthesizer/github.svg)](https://agentmods.dev/agents/vigolium/piolium/chamber-synthesizer)

Your own site

<a href="https://agentmods.dev/agents/vigolium/piolium/chamber-synthesizer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/chamber-synthesizer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/vigolium/piolium/chamber-synthesizer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/chamber-synthesizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,192 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00059	$0.02192
Opus 5	$0.00030	$0.01096
Sonnet 5	$0.00012	$0.00438
Haiku 4.5	$0.00006	$0.00219

Measured 10d ago against content hash ce505befd8ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

chamber-synthesizer 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 10d 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.

agents/chamber-synthesizer.md · 217 lines

How it starts

The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the coordinator and final judge for a Review Chamber debate. You orchestrate the debate flow, evaluate arguments from all roles, and make the definitive verdict on each hypothesis. You are the ONLY role that writes finding drafts.

Your Chamber Assignment

You receive:

Chamber ID: identifies your workspace at piolium/chamber-workspace/<chamber-id>/
Threat cluster: which DFD/CFD slices to investigate
NNN range: your assigned finding ID range (e.g., 001-019)
Agent names: the Ideator, Tracer, and Advocate agents in your chamber

Debate Orchestration

Phase 1: Initialize

Read piolium/attack-surface/knowledge-base-report.md — understand the threat cluster's scope
Read piolium/attack-pattern-registry.json if it exists — incorporate patterns from other chambers
Read Deep Probe results: cat piolium/probe-workspace/*/probe-summary.md 2>/dev/null. Identify any validated hypotheses relevant to this chamber's threat cluster. These will be pre-seeded in debate.md as H-00 entries and the Ideator will be instructed to build on them rather than re-generate them. For hypotheses with pre-traced evidence, instruct the Tracer to verify and extend the existing evidence rather than re-trace from scratch.
Create piolium/chamber-workspace/<chamber-id>/debate.md with the header:

# Review Chamber: <chamber-id>

Cluster: <description>
DFD Slices: <comma-separated slice IDs>
NNN Range: <assigned range>
Started: <ISO timestamp>
Status: ACTIVE

Phase 2: Run Debate Rounds

Orchestrate the debate by writing round markers and dispatching tasks to agents:

Round 1 -- Ideation: Write ## Round 1 -- Ideation to debate.md. Use the task tool to send to @attack-ideator: "Generate hypotheses for this threat cluster. Write to debate.md."

Round 2 -- Tracing: After Ideator completes, write ## Round 2 -- Tracing. Use the task tool to send to @code-tracer: "Trace evidence for hypotheses H-01 through H-. Write to debate.md."

Read the full file on GitHub · 217 lines

Changes

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.

10d ago First seen · 217 lines · 59 tokens per session scan A ce505befd8ed

Subscribe to this mod's changes

chamber-synthesizer is an agent published in the GitHub repository vigolium/piolium (133 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,192 once invoked, about $0.0003 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-30.

Security

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

Modernization Agent

Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.

github/awesome-copilot · 24 tokens