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 event4u-app/agent-config --skill judge-synthesisgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/judge-synthesis)<a href="https://agentmods.dev/skills/event4u-app/agent-config/judge-synthesis"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-synthesis/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/event4u-app/agent-config/judge-synthesis"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-synthesis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.03206 |
| Opus 5 | $0.00023 | $0.01603 |
| Sonnet 5 | $0.00009 | $0.00641 |
| Haiku 4.5 | $0.00005 | $0.00321 |
Grade A, and why
judge-synthesis 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 9d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
judge-synthesis
You are the synthesizer across an already-run set of judges. You do not run the judges and you do not re-judge — you consume their emitted verdict blocks and produce one structured report: a side-by-side verdict table, the consensus findings (flagged by ≥2 judges = highest confidence), the conflicts (judges that disagree), and a synthesized must-fix / should-fix / advisory split with per-finding judge provenance. No opaque single score. Never auto-gates — the human decides.
When to use
- Two or more judges have run on the same target and their verdict blocks need to become one decision-ready report.
- A mixed review spanning code judges + the artifact/defence judges (e.g. a PR that ships a roadmap + code + an injection-defense fixture) — no single existing command consolidates across all seven lenses.
/review-changesstep 5 (consolidation) wants the canonical synthesis format instead of an ad-hoc merge.
Do NOT use when:
- Only one judge ran — there is nothing to synthesize; surface that judge's block directly.
- You need to produce a verdict — that is the individual judge's job
(
judge-bug-hunter,judge-artifact-completeness,judge-injection-defense, etc.). - You are tempted to compute a single quality number — forbidden (see Do NOT).
Inputs
The verdict blocks the judges already emit. Each carries at minimum a judge name, a verdict, and zero or more findings with a severity. The three verdict vocabularies in the suite map onto one ordered severity axis:
| Judge family | Verdict vocabulary |
|---|---|
code judges (judge-bug-hunter, -code-quality, -security-auditor, -test-coverage, architecture-review-lens) |
apply / revise / reject |
judge-artifact-completeness |
complete / partial / incomplete |
judge-injection-defense |
defended / partial / breached |
judge-spec-compliance |
per criterion: SATISFIED / PARTIAL / MISSING — plus a criteria_source state that is not a verdict |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 268 lines · 46 tokens per session scan A 736c827588dd
judge-synthesis is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 3,206 once invoked, about $0.0002 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 skills, from other repositories
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
pr-blocker-summarizer
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.
receiving-code-review
Processes review feedback until the change is approved.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
session-start
Load handoff on session start, review lessons, output readiness signal. Triggers: '/session-start', 'start session'. Skip if: first session (no handoff), user requests 'start fresh', or standalone question unrelated to project context.
status
Display current progress of Draft tracks and active tasks. Shows phases, completion percentages, and blocked items.