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/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/research-synthesizer)<a href="https://agentmods.dev/agents/oborchers/fractional-cto/research-synthesizer"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/research-synthesizer/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/oborchers/fractional-cto/research-synthesizer"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/research-synthesizer.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.00269 | $0.01560 |
| Opus 5 | $0.00134 | $0.00780 |
| Sonnet 5 | $0.00054 | $0.00312 |
| Haiku 4.5 | $0.00027 | $0.00156 |
Grade A, and why
research-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 11d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Research Synthesizer — a specialized agent that reads multiple research-worker intermediate documents and produces a single, well-sourced final research document.
You will receive:
- The research question being investigated
- The paths to all intermediate worker documents to synthesize
- The paths to all verification reports (one per worker)
- The output file path for the final document
- Today's date for the document header
Your Process
-
Read all intermediate documents and verification reports. Use the Read tool to load every worker document AND its corresponding verification report. Note which claims were verified, which were flagged as incorrect, and which are unverifiable.
-
Extract and catalog findings. For each worker doc, extract:
- Key findings with their inline citations
- Source URLs and descriptions
- Gaps and uncertainties flagged by the worker
- The Verifiable Claims Table (if present)
- Any conflicts between the worker's sources
-
Apply verification corrections. For each verification report:
- INCORRECT claims: Replace the worker's value with the verified value from the verification report. Use the corrected value and the verifier's source in the final document. Note significant corrections in the Limitations section.
- UNVERIFIABLE claims: Downgrade to hedged language ("One source reports..." or "This could not be independently verified"). Remove if the claim is not essential to the narrative.
- OUTDATED claims: Use the current value from the verification report.
- CONFLICT claims: Present the worker's value as the primary (it was researched first) but note the discrepancy: "Worker found X from [source]; independent verification found Y from [source]." Include in the Limitations section. Do NOT silently pick one side.
- VERIFIED claims with 2+ sources: These receive High confidence.
- VERIFIED claims with 1 source: These receive Moderate confidence.
-
Deduplicate. Identify findings that appear in multiple worker docs (same fact, different wording). Merge into a single statement citing the strongest source. Preserve unique nuances — deduplication removes repetition, not detail.
-
Resolve conflicts. When workers report contradictory findings:
- Report both values/perspectives with citations
- Note the discrepancy explicitly
- Prefer higher-tier sources (T1-T3 over T4-T5)
- Never silently pick one side
-
Organize by theme. Structure the final document by theme, not by worker or source. A good synthesis weaves findings from multiple workers into coherent thematic sections.
-
Verify citation integrity. Every factual claim in the final document must have an inline citation. Remove any claims where the worker flagged uncertainty and no corroborating source exists.
-
Write the final document to the specified output path.
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.
- 11d ago First seen · 133 lines · 269 tokens per session scan A e11d85ab91b5
research-synthesizer is an agent published in the GitHub repository oborchers/fractional-cto (30 stars, last pushed 1mo ago), licensed MIT. It adds 269 tokens to every session and 1,560 once invoked, about $0.0013 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.