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/projectdxai/labrat/synthesizegit clone --depth 1 https://github.com/ProjectDXAI/labratWrote 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/projectdxai/labrat/synthesize)<a href="https://agentmods.dev/commands/projectdxai/labrat/synthesize"><img src="https://agentmods.dev/badge/commands/projectdxai/labrat/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.00000 | $0.00190 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
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.
What it actually says
Synthesize what the recent evaluations mean before dispatching more work. This step closes the gap between "config sweeper" and "research agent."
- Read the last ten entries in
state/evaluations.jsonland their corresponding records instate/candidates.jsonl. - Note the distribution of
failure_classvalues and the Pareto context ifstate/pareto.jsonexists. - Answer three questions in one compact paragraph each:
- What did we learn from the last ten evaluations that is not already in
coordination/prioritized_tasks.md? - Does this change which family should earn the next credit mint?
- Which decisive challenge is the next credible unlock, and which family is closest to winning it?
- What did we learn from the last ten evaluations that is not already in
- Write your synthesis to
coordination/prioritized_tasks.md, overwriting the prior content.
Do not dispatch new work in this step. The supervisor does that next.
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 · 12 lines · 0 tokens per session scan A bed93f11d67e
synthesize is a command published in the GitHub repository ProjectDXAI/labrat (239 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 190 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-08-30.
Other commands, from other repositories
riskreview
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
youtube-pulse
Summarize latest videos from tracked YouTube channels and extract short-term investment signals relevant to current holdings. Run after /market-pulse for context, or standalone for a quick opinion check.
mega-plan
Generate a mega-plan for project-level multi-feature orchestration. Breaks a complex project into parallel features with dependencies. Usage: /plan-cascade:mega-plan [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [design-doc-path].
pm-board
Open the great-pm board — a native, zero-dependency project board (hybrid stage×status Kanban + artifact panels + verdict metrics) served from the great-pm plugin itself. Self-contained, no npm packages.