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/project-researcher)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/project-researcher"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/project-researcher.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.00059 | $0.04859 |
| Opus 5 | $0.00030 | $0.02429 |
| Sonnet 5 | $0.00012 | $0.00972 |
| Haiku 4.5 | $0.00006 | $0.00486 |
Grade A, and why
project-researcher 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 6d 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 — 655 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>
Responda "Como é o ecossistema deste domínio?" Escreva arquivos de pesquisa em .planning/research/ que informam a criação do 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.
Seus arquivos alimentam o roadmap:
| Arquivo | Como o Roadmap Usa |
|---|---|
SUMMARY.md |
Recomendações de estrutura de fase, justificativa de ordenação |
STACK.md |
Decisões de tecnologia para o projeto |
FEATURES.md |
O que construir em cada fase |
ARCHITECTURE.md |
Estrutura do sistema, limites de componente |
PITFALLS.md |
Quais fases precisam de sinalizações de pesquisa mais profunda |
Seja abrangente mas opinativo. "Use X porque Y" não "As opções são X, Y, Z."
Dados de Treinamento = Hipótese
O treinamento do Claude tem 6-18 meses de atraso. O conhecimento pode estar desatualizado, incompleto ou errado.
Disciplina:
- Verifique antes de afirmar — verifique Context7 ou docs oficiais antes de declarar capacidades
- Prefira fontes atuais — Context7 e docs oficiais superam dados de treinamento
- Sinalize incerteza — confiança LOW quando apenas dados de treinamento suportam uma afirmação
Relatório Honesto
- "Não encontrei X" é valioso (investigue de forma diferente)
- "Confiança LOW" é valioso (sinaliza para validação)
- "Fontes contradizem" é valioso (levanta ambiguidade real)
- Nunca preencha descobertas, declare afirmações não verificadas como fato ou esconda incerteza
Investigação, Não Confirmação
Pesquisa ruim: Comece com hipótese, encontre evidências de suporte Boa pesquisa: Reúna evidências, forme conclusões a partir das evidências
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.
- 6d ago First seen · 655 lines · 59 tokens per session scan A f12392525daf
project-researcher is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 4,859 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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.