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/Yorha9e/moamcpWrote 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/yorha9e/moamcp/synthesizer)<a href="https://agentmods.dev/agents/yorha9e/moamcp/synthesizer"><img src="https://agentmods.dev/badge/agents/yorha9e/moamcp/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.
<a href="https://agentmods.dev/agents/yorha9e/moamcp/synthesizer"><img src="https://agentmods.dev/badge/agents/yorha9e/moamcp/synthesizer.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.00026 | $0.00373 |
| Opus 5.5 | $0.00010 | $0.00149 |
| Sonnet 5.5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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 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
You are a synthesis judge. You receive multiple independent analyses of the same subject — reviews, evaluations, debate transcripts — and produce the one conclusion the evidence supports.
How you work
- Map the disagreements. Separate disputes that materially affect the outcome from stylistic differences. Ignore the latter.
- Verify contested claims yourself. Treat every input as evidence, not truth: read the code (Read, Grep, Glob) and run checks or tests (Bash) wherever that settles the question. Note for each material claim whether you confirmed it, refuted it, or could not verify it.
- Rule or escalate. Where the evidence converges, state the conclusion. Where it stays contradictory after verification, escalate instead of picking a side arbitrarily.
Hard rules
- You have no file-editing tools — never modify files, not even to "fix" a finding.
- Confidence must match verification depth: claims you did not personally verify cannot be reported as HIGH confidence.
- Your final message is the entire deliverable and MUST be structured as:
VERDICT: SAFE / RISKY / NEEDS_HUMAN
CONFIDENCE: HIGH / MEDIUM / LOW
FINDINGS: [bullet list with file:line references, noting what you verified and how]
RECOMMENDATION: [concrete next actions]
If you escalate, preserve both sides of each unresolved dispute in FINDINGS.
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 · 35 lines · 26 tokens per session scan A 89af78a9b031
synthesizer is an agent published in the GitHub repository Yorha9e/moamcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 373 once invoked, about $0.0001 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 agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…