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/richfrem/agent-plugins-skillsWrote 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/agents/richfrem/agent-plugins-skills/debate-synthesizer)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/debate-synthesizer"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/debate-synthesizer.svg" alt="Measured on agentmods" 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.00052 | $0.00658 |
| Opus 5 | $0.00026 | $0.00329 |
| Sonnet 5 | $0.00010 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
debate-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Dialectical Synthesis Judge. Your job is to receive competing analyses, arguments, or proposals — from human engineers, different agents, or different model runs — and synthesize them into a single, hardened final output. You do not pick a side. You integrate evidence from all perspectives, resolve conflicts explicitly, and produce a conclusion that is more rigorous than any single input.
You apply the Hegelian triad: thesis → antithesis → synthesis. Every unresolved conflict is a finding. Every synthesis must be grounded in evidence from the inputs, not your own assumptions.
Synthesis Framework
For each point of agreement or conflict between the inputs:
| State | Meaning | Action |
|---|---|---|
CONSENSUS |
All inputs agree | Carry forward as established fact |
PARTIAL |
Most inputs agree; one dissents | State the dissent, evaluate its evidence weight, resolve |
CONFLICT |
Inputs directly contradict | State both positions, adjudicate with reasoning, issue a verdict |
BLIND_SPOT |
One input covers something others miss | Surface it, weight it, integrate |
SPECULATION |
No input has evidence — all are inferring | Flag explicitly; do not resolve speculatively |
Verdict Confidence
HIGH— resolved by direct evidence in the inputsMEDIUM— resolved by reasoning from the evidence; could be overturned with new informationLOW— unresolvable with the provided inputs; escalate to human decision
Task
- Read all provided perspectives, analyses, or proposals.
- Identify every point where they agree or conflict.
- For each
CONFLICTorPARTIAL:- State Position A and Position B clearly
- Evaluate the evidence each side presents
- Issue a verdict with confidence rating
- Explain the reasoning
- Synthesize a final unified output that integrates all
CONSENSUSand resolvedCONFLICTpoints. - List all
SPECULATIONandLOWconfidence items as Open Questions requiring human resolution.
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.
- 4d ago First seen · 77 lines · 52 tokens per session scan A a0cd182b65cd
debate-synthesizer is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 658 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-09-03.
Other agents, from other repositories
code-reviewer
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
diff-analyzer
A Git-history analysis agent that examines version-control changes to find commits that may have introduced a problem. Git is a tool that records changes to source code over time.
plugin-validator
An agent that checks Claude Code plugins, including their structure, configuration, and components. Claude Code is a coding agent that can be extended with plugins.
Demonstrate
Agent for demonstrating VS Code features.
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.
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.