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 commands/lhl/realitycheck/synthesizegit clone --depth 1 https://github.com/lhl/realitycheckWrote 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/commands/lhl/realitycheck/synthesize)<a href="https://agentmods.dev/commands/lhl/realitycheck/synthesize"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/synthesize.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.00011 | $0.00693 |
| Opus 5 | $0.00005 | $0.00347 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
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 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reality:synthesize - Cross-Source Synthesis
Create a cross-source synthesis across multiple source analyses and existing claims.
Use this after running /reality:check on multiple sources (or when relevant source analyses already exist and you want a higher-level conclusion).
Usage
/reality:synthesize <topic>
Output
Write a synthesis document to:
analysis/syntheses/<synth-id>.md
The synthesis should link back to relevant source analyses in:
analysis/sources/<source-id>.md
Workflow
- Define the question
- What is this synthesis trying to answer?
- Collect inputs
- Prefer existing source analyses in
analysis/sources/ - If a relevant source has no analysis yet, run
/reality:checkfirst (or explicitly record the gap)
- Prefer existing source analyses in
- Write the synthesis
- Points of agreement (which claims converge?)
- Points of disagreement (where do they conflict, and why?)
- Conclusions with calibrated credence + key uncertainties
- Link claim IDs and source analysis files wherever possible
- Neutral Analyst Prose Pass
- Apply this pass to the analyst's prose, not source text, direct quotes, titles, quoted slogans, or persuasion/rhetoric examples.
- Remove rhetorical setup, marketing language, vague intensifiers, hedge stacks, and conclusion recaps from analyst prose.
- Preserve source wording when it is evidence for rhetoric, framing, or persuasion; label it as source language instead of adopting it as the analyst's voice.
- (Optional) Register an argument chain
- If the synthesis centers on a specific argument chain, register it and point
--analysis-fileat the synthesis document:
- If the synthesis centers on a specific argument chain, register it and point
"${CLAUDE_PLUGIN_ROOT}/scripts/run-db.sh" chain add \
--id "CHAIN-YYYY-NNN" \
--name "..." \
--thesis "..." \
--claims "TECH-2026-001,ECON-2026-002" \
--analysis-file "analysis/syntheses/<synth-id>.md"
- Validate
"${CLAUDE_PLUGIN_ROOT}/scripts/run-validate.sh"
- Update README
- Add a row to the "Syntheses" table (kept above "Source Analyses") in your data repo
README.md.
- Add a row to the "Syntheses" table (kept above "Source Analyses") in your data repo
- Commit and push
- If you ran a DB write command (e.g.,
chain add), the plugin hook may auto-commit. - Otherwise, commit your
analysis/+README.mdchanges manually.
- If you ran a DB write command (e.g.,
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 · 80 lines · 11 tokens per session scan A e92ca511168d
synthesize is a command published in the GitHub repository lhl/realitycheck (41 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 693 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-30.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
智能生成 Git 提交信息并提交.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
requirement-review
需求文档多角色评审（requirement-review）：需求文档 → 7-Agent 并行评审 → 重构高质量需求文档（Runtime 受控流程，0-7 阶段状态机）.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.