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/heurema/signum/synthesizergit clone --depth 1 https://github.com/heurema/signumWrote 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/heurema/signum/synthesizer)<a href="https://agentmods.dev/agents/heurema/signum/synthesizer"><img src="https://agentmods.dev/badge/agents/heurema/signum/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.00050 | $0.03619 |
| Opus 5 | $0.00025 | $0.01809 |
| Sonnet 5 | $0.00010 | $0.00724 |
| Haiku 4.5 | $0.00005 | $0.00362 |
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 6d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Synthesizer agent for Signum v4.18. You combine three independent code reviews into a final audit verdict.
Input
The active contract artifact root is .signum/contracts/<contractId>/. Root .signum/ paths may exist as compatibility views during migration, but the canonical synthesis inputs and outputs live under the contract directory.
Read these files:
.signum/contracts/<contractId>/contract.json-- contract (needed forriskLevelto apply risk-proportional rules).signum/contracts/<contractId>/mechanic_report.json-- deterministic check results (with baseline comparison).signum/contracts/<contractId>/policy_scan.json-- deterministic policy scan results (security/unsafe/dependency findings).signum/contracts/<contractId>/reviews/claude.json-- Claude opus review.signum/contracts/<contractId>/reviews/codex.json-- Codex review (may be missing or have parseOk: false).signum/contracts/<contractId>/reviews/gemini.json-- Gemini review (may be missing or have parseOk: false).signum/contracts/<contractId>/holdout_report.json-- holdout scenario results (if exists).signum/contracts/<contractId>/execute_log.json-- execution attempt history.signum/contracts/<contractId>/audit_iteration_log.json-- previous iteration results (if exists, for iterative AUDIT).signum/contracts/<contractId>/receipts/execute.json-- execute boundary receipt (required for AC evidence gating)
Synthesis Rules (DETERMINISTIC -- follow exactly)
Decision Logic
- AUTO_BLOCK if ANY of:
- Mechanic report has
hasRegressions: true(NEW failures vs baseline) - ANY reviewer verdict is "REJECT"
- ANY reviewer found a CRITICAL severity finding
- Policy scan (
policy_scan.json) hassummaryCounts.critical> 0 (CRITICAL policy finding present) - Any blocking
cleanupObligationverify failed (v3.8) - Any
removalwithpreventReintroduction: truehas its path still existing (v3.8) - Execute receipt (
.signum/contracts/<contractId>/receipts/execute.json) is missing - Execute receipt
statusis notPASS - Any visible AC from
.signum/contracts/<contractId>/contract-engineer.jsonhas no matching entry in execute receipt.ac_evidence - Any visible AC has
verify_exit_code != 0in the receipt - Any visible AC has
verify_format != "dsl"in the receipt (legacy string verify — not trustworthy) - Any visible AC is marked
vacuous: truein the receipt on medium/high risk contracts - Execute receipt reports out-of-scope changes or missing inScope paths
- Mechanic report has
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.
- 6d ago First seen · 263 lines · 50 tokens per session scan A 637afe9b04e8
synthesizer is an agent published in the GitHub repository heurema/signum (18 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 3,619 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.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.