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/aidemd-mcp/server/synthesizegit clone --depth 1 https://github.com/aidemd-mcp/serverWrote 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/aidemd-mcp/server/synthesize)<a href="https://agentmods.dev/commands/aidemd-mcp/server/synthesize"><img src="https://agentmods.dev/badge/commands/aidemd-mcp/server/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.00649 |
| Opus 5 | $0.00000 | $0.00324 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aide:synthesize — Synthesize Phase
Agent: This command is executed by the
aide-strategistagent.
Read the intent spec's frontmatter and the brain's research, then fill in the .aide body sections (Context, Strategy, Good examples, Bad examples, References) AND author the sibling brief.aide. This is a fresh strategist session — it did not run the research phase and carries no prior context.
Synthesize is conditional in the AIDE pipeline. It runs only when the orchestrator routes through this phase — either because the spec-writer signaled "Strategy needed" or the user explicitly asked for synthesis. Most modules skip synthesize and go straight to /aide:plan as frontmatter-only navigation stubs.
All-or-nothing rule: if you produce a body, you fill all five sections. Partial bodies (Context filled but Strategy empty, etc.) are forbidden. If the available research isn't sufficient to fill all five, escalate back to /aide:research rather than producing a thin body.
Checklist
- Read the target
.aidefile. Confirm frontmatter is complete (scope, intent, outcomes.desired, outcomes.undesired). If frontmatter is missing or incomplete, stop and escalate back to/aide:spec - Identify the domain from the intent. Search the brain for research filed under that domain (e.g.,
research/email-marketing/,research/local-seo/) - If no brain is available, check for a co-located
research.aidein the same folder as the intent spec - If neither brain research nor
research.aideexists, stop — research must run first via/aide:research - Read all relevant research entries. Cross-reference findings against the intent's
outcomes.desiredandoutcomes.undesired— the research serves the intent, not the other way around - Fill
## Context— why this module exists, the domain-level problem, constraints that shape it. Write for a generalist engineer. No code. Do not restate context already carried by a parent.aide - Fill
## Strategy— distill research into decisions. Each paragraph names a concrete choice (tactic, threshold, structural decision) and the reasoning or data that justifies it. Cite sources inline. Write in decision form, not description form. No code - Fill
## Good examples— concrete domain output that illustrates success. Real output, not code. Pattern material for QA - Fill
## Bad examples— the almost-right failures. Output that looks valid but violates intent. Recognizable failure modes, not enumeration - Verify every strategy decision traces back to an
outcomes.desiredor guards against anoutcomes.undesired. Cut anything that doesn't serve the intent - Run
aide_validateto check the completed spec for structural issues - Hand off to
/aide:plan— the architect is the next phase
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 · 25 lines · 0 tokens per session scan A 6a0b4628374b
synthesize is a command published in the GitHub repository aidemd-mcp/server (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 649 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-31.
Other commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
ijfw-metrics
Show IJFW token / cost / session metrics over a time window. Reads .ijfw/metrics/sessions.jsonl via the ijfwmetrics MCP tool.
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.