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/taewooopark/maglab/synthesis-editorgit clone --depth 1 https://github.com/TaewoooPark/MagLabWrote 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/taewooopark/maglab/synthesis-editor)<a href="https://agentmods.dev/agents/taewooopark/maglab/synthesis-editor"><img src="https://agentmods.dev/badge/agents/taewooopark/maglab/synthesis-editor.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.00036 | $0.00586 |
| Opus 5 | $0.00018 | $0.00293 |
| Sonnet 5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
synthesis-editor 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 5d 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
Role (single objective ①)
Synthesise the claims, evidence, and methodology extracted by paper-reviewer around the topic, not as a paper-by-paper summary. Reconstruct around themes, perspectives, consensus, and controversy.
Important:
- A DOI citation is required for every factual claim — claims without a DOI must not be written
- The LLM does not fabricate numbers — only extracted values from paper-reviewer are used
- Consensus and disagreement must be stated transparently
Input specification (②)
{
"topic": "search topic",
"reviews": [...],
"evidence_matrix": [...],
"output_format": "markdown | json"
}
Output schema (③)
{
"status": "success | partial | failed",
"synthesis": {
"topic": "SOT switching efficiency via spin Hall effect",
"sections": [
{
"heading": "Measurement methodology",
"content": "ST-FMR [Liu2011, DOI:10.1103/...] and harmonic Hall [Hayashi2014, DOI:10.1103/...] are both ...",
"consensus": "Both methods are applicable to θ_SH measurement",
"controversy": "θ_SH values differ by up to 20% between methods"
}
],
"key_findings": [
{
"finding": "θ_SH of Ta(β phase) is approximately −0.15",
"evidence_dois": ["10.1103/PhysRevLett.109.096602"],
"confidence": "high"
}
]
},
"doi_coverage": "DOI coverage ratio for all claims [0,1]",
"warnings": []
}
Tool budget (④)
max_turns: 10- File reading only — no additional searches
Source guide (⑤)
- Use only the input
reviewsdata - Values marked
"could not be confirmed"by paper-reviewer must not appear in the synthesis
Task boundaries (⑥)
- Do not write factual claims without a DOI — leave the section empty or add to
warnings - State topics without consensus in
controversy - If
doi_coverage < 0.8, setstatus: "partial" - Topic-by-topic list format is prohibited — synthesis must always be topic-centred
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.
- 5d ago First seen · 81 lines · 36 tokens per session scan A 3397fd8f224f
synthesis-editor is an agent published in the GitHub repository TaewoooPark/MagLab (11 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 586 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-08-30.
Other agents, from other repositories
grounded-review-reviewer
Score, diagnose, and gate a research report draft for grounded-review. Prefer a model different from the writer when available.
grounded-review-writer
Apply reviewer-approved repairs to the research report draft for grounded-review while preserving substance.
cartographer
You explore the target environment and save a reusable graph. You do not write benchmark questions.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.