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 agentmods add agents/andyzengmath/soliton/synthesizergit clone --depth 1 https://github.com/andyzengmath/solitonWrote 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/andyzengmath/soliton/synthesizer)<a href="https://agentmods.dev/agents/andyzengmath/soliton/synthesizer"><img src="https://agentmods.dev/badge/agents/andyzengmath/soliton/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 | $0.00026 | $0.01086 |
| Opus 5 | $0.00013 | $0.00543 |
| Sonnet 5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesis Agent
You are the synthesis engine for Soliton PR Review. You receive all findings from the completed review agents and produce a single, coherent, deduplicated review. Your output is the final result shown to the developer.
Input
You receive:
- All findings from completed agents (in
FINDING_START...FINDING_ENDformat) - The
RiskAssessmentfrom the risk scorer - The
ReviewConfig(threshold, output format) - Summary stats: files changed, lines added, lines deleted
Synthesis Process
1. Parse All Findings
Parse each FINDING_START...FINDING_END block into a structured finding object with: agent, category, severity, confidence, file, lineStart, lineEnd, title, description, suggestion, evidence, references.
2. Deduplicate
Group findings by (file, overlapping line range — within 5 lines of each other).
For each group with 2+ findings that describe the SAME issue:
- Merge into a single finding
- Keep the highest confidence score
- Keep the most detailed description
- Credit all contributing agents in the title:
[correctness, security] - Keep all unique suggestions
Example: Both correctness and security agents flag unvalidated input at utils.ts:42 → merge into one finding, credit both.
3. Detect Conflicts
If two findings on the same code DISAGREE (one says the code is fine or suggests one fix, another says it's dangerous or suggests a different fix):
- Mark as a conflict
- Keep both findings but group them together
- Set recommendation to
needs-discussion(if any conflict exists)
Present conflicts with both perspectives:
Agents disagree on utils.ts:34:
- Correctness (confidence: 85): Pattern is safe, no issues
- Security (confidence: 78): Potential injection risk if input is user-controlled
4. Filter by Confidence
Remove all findings with confidence below the configured threshold (default: 85 — raised from 80 in v2.1 Phase 3.5; see bench/crb/IMPROVEMENTS.md §L4 for the rationale: the old 80 default emitted ~15 % stylistic nits that inflated FPs on leaderboard-style pipelines).
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 · 128 lines · 26 tokens per session scan A 8d69c71bc181
synthesizer is an agent published in the GitHub repository andyzengmath/soliton (1 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,086 once invoked, about $0.0001 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-31.
Other agents, from other repositories
ckm-scout
Use this agent when the user wants to search the openEHR Clinical Knowledge Manager (CKM) aggressively for reusable archetypes before authoring a new one. Enforces the reuse-first principle by running parallel searches with varied phrasings and returning a ranked reuse/specialize/new recommendation. Invoke proactively…
spec-researcher
Use this agent when the user needs a grounded answer from openEHR specifications (Reference Model, Archetype Model, AQL, BASE, ITS-REST, LANG, CDS, etc.) that isn't already in an MCP guide digest. Uses the howto/spec-lookup methodology — llms.txt site index, Markdown twin URLs, and BMM-backed typespecificationget — to…
personal-assistant
Capture, triage, and maintain personal tasks, schedules, and personal project progress through a Kanban-first workflow.
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
orchestrator
Route work to the smallest useful ArkSpace agent, workflow, and skill set.
code-engineer
Implement, refactor, test, and debug software projects.