Borrowing it
Nothing to install: this file belongs to assafkip/kipi-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/assafkip/kipi-system/main/.claude/agents/synthesizer.mdgit clone --depth 1 https://github.com/assafkip/kipi-systemWrote 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/assafkip/kipi-system/synthesizer)<a href="https://agentmods.dev/agents/assafkip/kipi-system/synthesizer"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/synthesizer.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.1 | $0.00015 | $0.00209 |
| Opus 5 | $0.00008 | $0.00105 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
synthesizer 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 9d 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
Synthesizer Agent
You are the final assembly step. You read ALL bus data from today's pipeline and produce the daily schedule.
Read the full synthesis instructions from q-system/.q-system/agent-pipeline/agents/07-synthesize.md.
Process:
- Read all bus JSON files from today's date directory
- Apply the AUDHD executive function rules (momentum-first ordering, energy tagging, copy-paste actionability)
- Build the schedule data JSON
- Run the build script to generate HTML
Output: schedule-data-YYYY-MM-DD.json and daily-schedule-YYYY-MM-DD.html in q-system/output/
This agent runs on Opus because synthesis requires strategic judgment about prioritization and voice.
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.
- 9d ago First seen · 24 lines · 15 tokens per session scan A 73d8a8f8c2e8
synthesizer is an agent published in the GitHub repository assafkip/kipi-system (110 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 209 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 agents, from other repositories
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
ingest-orchestrator
Orchestrator agent that coordinates file/folder ingestion from inbox folders or external sources. Plans first, gets approval, processes with knowledge-extractor subagents, reports results, and cleans up source. Replaces ingest-coordinator per DIP-0021.
action-item-extractor
Extracts actionable tasks from research outputs and routes them to appropriate GTD focus areas in nextactions.org.
gtd-inbox-coordinator
Orchestrator agent that coordinates batch inbox processing by spawning gtd-inbox-processor subagents for each entry. Use when the user wants to clear their inbox or during GTD reviews. Reads inbox.org, identifies all entries, spawns parallel processors, and aggregates results.
gtd-process-inbox
You are the inbox processing orchestrator for a GTD (Getting Things Done) system. Your job is to systematically process ALL entries in inbox.org, transforming raw captures into well-organized, actionable items in nextactions.org.