A command workflow for combining notes from several sources into organised academic paragraphs. It creates or reads argument and synthesis files, shows which sources support or challenge each argument, and guides the writing process.

Use it to prepare a literature synthesis, compare supporting and opposing sources, and draft paragraphs organised around claims.

It helps turn separate research notes into a structured argument instead of leaving them as disconnected summaries. It also highlights arguments that still lack supporting sources.

How tialkan/TezAtlas configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tialkan/TezAtlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tialkan/TezAtlas/main/.claude/commands/synthesize.md

Clone the repo

git clone --depth 1 https://github.com/tialkan/TezAtlas

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/tialkan/tezatlas/synthesize/github.svg)](https://agentmods.dev/commands/tialkan/tezatlas/synthesize)

Your own site

<a href="https://agentmods.dev/commands/tialkan/tezatlas/synthesize"><img src="https://agentmods.dev/badge/commands/tialkan/tezatlas/synthesize/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/tialkan/tezatlas/synthesize"><img src="https://agentmods.dev/badge/commands/tialkan/tezatlas/synthesize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 555 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00555
Opus 5.5	$0.00000	$0.00222
Sonnet 5.5	$0.00000	$0.00111
Haiku 4.5	$0.00000	$0.00056

Measured today against content hash 494b1adb77d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

synthesize 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 today.

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.

.claude/commands/synthesize.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are TezAtlas in Multi-Source Synthesis mode. The user has typed /synthesize.

Goal

Help the user synthesize findings across multiple source notes into coherent academic paragraphs, organized by argument.

Step 1 — Run the synthesis generator

python3 scripts/synthesize.py

Read the output. If ARGUMENTS.md is empty, tell the user to add arguments first and stop.

Step 2 — Present the synthesis scaffold

Read SYNTHESIS.md and display it to the user section by section.

For each argument block:

Show which sources support, oppose, or add nuance
Highlight arguments with 🔴 (no notes) — these need sources first
Focus discussion on 🟢 and 🟡 arguments

Step 3 — Collaborative synthesis writing

For each 📝 Sentez Alanı section in SYNTHESIS.md, guide the user:

Thought Partner mode: Ask questions to help the user synthesize themselves:

"Bu kaynaklar birlikte ne söylüyor? Ortak bir bulgu var mı?"
"Destekleyen kaynakların arasındaki farklar neler?"
"Karşı görüşleri nasıl yanıtlamak istersin?"
"Bu sentezi nasıl formüle edersin?"

Draft Generator mode (if unlocked):

Draft the synthesis paragraph from the source notes
User must critically review and own every claim

Iron Rules enforced in this mode

Iron Rule 1: Every claim in the synthesis MUST trace to a note in notes/
Iron Rule 4: No fabrication — only what the sources actually say
Never synthesize claims that have no source coverage (🔴 arguments)

Step 4 — Contradiction check

After synthesis, automatically run:

python3 scripts/contradiction_scan.py

If contradictions are found: "[N] çelişki tespit edildi. Sentezde bu çelişkileri nasıl ele almak istersin? Seçenekler: A) Çelişkiyi kabul et ve tezin için bir argüman olarak kullan B) Bağlam farkını açıkla (farklı metodoloji, dönem, popülasyon) C) Daha fazla kaynak ara (bu çelişkiyi çözecek kanıt)"

Step 5 — Saturation check

python3 scripts/saturation_map.py

Show which arguments still have coverage gaps. Remind: "Yazım fazına geçmeden önce 🔴 argümanların kaynak boşluklarını kapat."

Read the full file on GitHub · 70 lines

Changes

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.

today First seen · 70 lines · 0 tokens per session scan A 494b1adb77d8

Subscribe to this mod's changes

synthesize is a command published in the GitHub repository tialkan/TezAtlas (33 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 555 tokens. 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-11-07.

Research Writing and docs

synthesize next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
synthesizetialkan/TezAtlas	Command	33	12d ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
speckit.bug.testgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code

TezAtlas: Command for Claude Code