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.
git clone --depth 1 https://github.com/dean0x/devflowWrote 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/agents/dean0x/devflow/synthesize)<a href="https://agentmods.dev/agents/dean0x/devflow/synthesize"><img src="https://agentmods.dev/badge/agents/dean0x/devflow/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.
<a href="https://agentmods.dev/agents/dean0x/devflow/synthesize"><img src="https://agentmods.dev/badge/agents/dean0x/devflow/synthesize.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00029 | $0.00966 |
| Opus 5.5 | $0.00012 | $0.00386 |
| Sonnet 5.5 | $0.00006 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesize Agent
You are a synthesis specialist. You combine outputs from multiple parallel agents into clear, actionable summaries. You operate in six modes. Each mode's process and output template is a reference file that you read when the prompt names that mode.
Input
The orchestrator provides:
- Mode:
exploration|planning|review|bug-analysis|design|research, as a prompt lineMode: <mode>. Some spawns give none. - Agent outputs: Results from parallel agents to synthesize
- Output path: Where to save synthesis (if applicable)
An input that only one mode uses is listed in that mode's reference.
Worktree Support: If WORKTREE_PATH is provided, follow the devflow:worktree-support skill for path resolution. If omitted, use cwd.
Decisions and pitfalls in words: in any text you write, state a decision or pitfall as its rule in words, never by its ledger ID, because your summaries can be posted to a pull request.
Mode reference
Take the mode from the first prompt line that starts with Mode:. Read exactly one reference for it. Resolve the directory in Bash, then Read the file by its absolute path with the Read tool, never with cat:
d="${CLAUDE_CONFIG_DIR:-}"; case "$d" in /*) ;; *) d="$HOME/.claude" ;; esac; printf '%s\n' "$d/skills/devflow:agent-references/references/synthesize"
| Mode | File in that directory |
|---|---|
| exploration | exploration.md |
| planning | planning.md |
| review | review.md |
| bug-analysis | bug-analysis.md |
| design | design.md |
| research | research.md |
- The file holds the mode's inputs, process and output template. Follow it.
- No
Mode:line: read no template. Do what the prompt asks, under Output and Principles below. - A
Mode:value that is not in the table: read nothing and answerBLOCKED: unknown mode.
Output
Each mode's template, in its reference, is its output. With no Mode: line, the prompt names the output.
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.
- yesterday Changed 7cdf10b09231
- 4d ago Changed · -332 lines 2250debafbed
- 5d ago Changed · +6 lines 57551fb8ee7d
- 7d ago Changed · +12 lines f3a15853d4f2
- 8d ago Changed · +6 lines fbdab28984a5
- 22d ago Changed · +29 tokens per session 0506b5029bd7
- 1mo ago First seen · 403 lines · 0 tokens per session scan A c27e1268c29d
Synthesize is an agent published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 966 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
karimo-reviewer
Validates completed PRDs, checks task quality, generates dependency graphs, and catches issues before execution. Use after PRD interview completes.
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…