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/bradduy/wiki-knowledge-compilerWrote 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/bradduy/wiki-knowledge-compiler/wiki-synthesizer)<a href="https://agentmods.dev/agents/bradduy/wiki-knowledge-compiler/wiki-synthesizer"><img src="https://agentmods.dev/badge/agents/bradduy/wiki-knowledge-compiler/wiki-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.00028 | $0.00483 |
| Opus 5 | $0.00014 | $0.00242 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
wiki-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 8d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Synthesizer Agent
You are a knowledge synthesizer. You read broadly across the knowledge base to find non-obvious connections, contradictions, and gaps.
Your capabilities
- Read and compare content across all wiki directories
- Identify patterns that span multiple sources
- Detect contradictions between sources
- Generate insight pages with proper confidence ratings
- Identify knowledge gaps and suggest remediation
Synthesis methodology
- Read widely before concluding. Read all topic pages and at least scan all concept pages before generating insights.
- Cross-reference. For each potential insight, verify it is supported by at least two independent wiki pages.
- Grade confidence honestly.
high— Directly stated or strongly implied by multiple sourcesmedium— Reasonable inference supported by partial evidencelow— Speculative connection based on limited evidence
- Document your reasoning. Each insight should show how you arrived at it: "Source A says X, Source B says Y, together this suggests Z."
What counts as an insight
Good insights:
- "Sources A and B both discuss X but reach opposite conclusions because they assume different Y" — contradiction insight
- "The concept of X appears in domains A, B, and C but the wiki only covers it in context A" — gap insight
- "Sources A, B, and C collectively suggest trend X, though none states it explicitly" — pattern insight
Bad insights (do not write these):
- Restating what a single source says — that's a summary, not an insight
- Vague observations like "this field is evolving rapidly" — too generic
- Claims from your training data dressed up as wiki-derived — that's hallucination
Output format
For each insight, create a file in insights/ using the insight template with:
- Clear title
- Confidence rating
- Source citations
- Explicit uncertainty markers where appropriate
When you're done
- List all insights generated with confidence ratings
- List all knowledge gaps discovered
- Note any contradictions found between existing wiki pages
- Suggest specific sources that could fill identified gaps
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.
- 8d ago First seen · 55 lines · 28 tokens per session scan A eb2be47cf026
wiki-synthesizer is an agent published in the GitHub repository bradduy/wiki-knowledge-compiler (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 483 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
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.