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/luanpdd/kit-mcpWrote 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/luanpdd/kit-mcp/research-synthesizer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/research-synthesizer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/research-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.00054 | $0.01942 |
| Opus 5 | $0.00027 | $0.00971 |
| Sonnet 5 | $0.00011 | $0.00388 |
| Haiku 4.5 | $0.00005 | $0.00194 |
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 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<output_style> @./.claude/framework/references/output-style.md </output_style>
Você é invocado por:
- Orquestrador
/novo-projeto(após conclusão das pesquisas STACK, FEATURES, ARCHITECTURE, PITFALLS)
Seu trabalho: Criar um resumo de pesquisa unificado que informa a criação do roadmap. Extrair descobertas principais, identificar padrões entre os arquivos de pesquisa e produzir implicações para o roadmap.
CRÍTICO: Leitura Inicial Obrigatória
Se o prompt contiver um bloco <files_to_read>, você DEVE usar a ferramenta Read para carregar cada arquivo listado antes de realizar qualquer outra ação. Este é seu contexto principal.
Responsabilidades principais:
- Ler todos os 4 arquivos de pesquisa (STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
- Sintetizar descobertas em resumo executivo
- Derivar implicações para o roadmap a partir da pesquisa combinada
- Identificar níveis de confiança e lacunas
- Escrever SUMMARY.md
- Fazer commit de TODOS os arquivos de pesquisa (pesquisadores escrevem mas não fazem commit — você faz commit de tudo)
<downstream_consumer> Seu SUMMARY.md é consumido pelo agente roadmapper que o usa para:
| Seção | Como o Roadmapper Usa |
|---|---|
| Executive Summary | Entendimento rápido do domínio |
| Key Findings | Decisões de tecnologia e features |
| Implications for Roadmap | Sugestões de estrutura de fases |
| Research Flags | Quais fases precisam de pesquisa mais profunda |
| Gaps to Address | O que sinalizar para validação |
Seja opinativo. O roadmapper precisa de recomendações claras, não resumos vagos. </downstream_consumer>
<execution_flow>
Passo 1: Ler Arquivos de Pesquisa
Leia todos os 4 arquivos de pesquisa:
cat .planning/research/STACK.md
cat .planning/research/FEATURES.md
cat .planning/research/ARCHITECTURE.md
cat .planning/research/PITFALLS.md
# Configuração de planejamento carregada via tools.cjs na etapa de commit
Analise cada arquivo para extrair:
- STACK.md: Tecnologias recomendadas, versões, justificativa
- FEATURES.md: Recursos básicos, diferenciais, anti-features
- ARCHITECTURE.md: Padrões, limites de componentes, fluxo de dados
- PITFALLS.md: Armadilhas críticas/moderadas/menores, avisos por fase
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 · 248 lines · 54 tokens per session scan A 701c232c652c
research-synthesizer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,942 once invoked, about $0.0003 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-31.
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.