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/dormstern/forge/synthesizegit clone --depth 1 https://github.com/dormstern/forgeWhat 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.00531 |
| Opus 5 | $0.00018 | $0.00266 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
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 2d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:synthesize — Thesis synthesis (Founder mode)
Execution mode: direct. This command has explicit steps below — execute them in order. Do not enter plan mode, do not write a plan file, do not call ExitPlanMode. The framework already did the planning; you just run the steps.
You dispatch the thesis-synthesizer agent to update THESIS.md based on the cycle's evidence and DA report.
Behavior
-
Read
THESIS.md(all 7 sections + current confidence),evidence.json(new evidence from this cycle),interviews.md(latest summaries),cycles.json(last 2 cycles for trajectory), and the latest DA report. -
Dispatch thesis-synthesizer to:
- Map new evidence to thesis sections (with evidence IDs)
- Audit claims (UNSUPPORTED / WEAK / CONTESTED)
- Score confidence per section using the 1–5 rubric with hard caps:
- Single source type → cap 3
- Two source types → cap 4
- Unaddressed contradictions → cap 3
- All stated intent (no behavioral) → cap 3
- ≥4 requires ≥50% behavioral evidence AND ≥3 source types
- 5 requires behavioral evidence AND commitments
- Append an Evolution Log entry (changes, trigger evidence, confidence delta)
- Identify the weakest section and propose specific next-cycle tests
-
Update
THESIS.mdwith new scores. Updatecycles.jsonwith this cycle'sconfidence_snapshotandconfidence_delta. -
PAUSE — Present the synthesis report. The user reviews and accepts or challenges the scores. Conservative scoring is the default; argue up only if the user provides specific evidence.
Constraints
- Confidence cannot increase without new evidence.
- Contradicting evidence is never removed — only addressed.
- Stagnation across 2+ cycles → flag for methodology review.
- Trajectory down 2+ cycles → consider PIVOT or KILL recommendation.
Reference
- Agent: agents/thesis-synthesizer.md
- Rubric: skills/evidence-weighting/SKILL.md
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.
- 2d ago First seen · 44 lines · 36 tokens per session scan A 0c2929b2024e
synthesize is a command published in the GitHub repository dormstern/forge (6 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 531 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.