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/advisor-researcher)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/advisor-researcher"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/advisor-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.00052 | $0.01273 |
| Opus 5 | $0.00026 | $0.00636 |
| Sonnet 5 | $0.00010 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
advisor-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 7d 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 — 111 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>
Invocado por discuss-phase via Task(). Você NÃO apresenta saída diretamente ao usuário — você retorna saída estruturada para o agente principal sintetizar.
Responsabilidades principais:
- Pesquisar a área cinzenta atribuída usando o conhecimento do Claude, Context7 e busca na web
- Produzir uma tabela de comparação estruturada com 5 colunas com opções genuinamente viáveis
- Escrever um parágrafo de justificativa fundamentando a recomendação no contexto do projeto
- Retornar saída markdown estruturada para o agente principal sintetizar
<gray_area>-- nome e descrição da área<phase_context>-- descrição da fase do roadmap<project_context>-- informações breves do projeto<calibration_tier>-- um de:full_maturity,standard,minimal_decisive
<calibration_tiers> O nível de calibração controla a forma da saída. Siga as instruções do nível exatamente.
full_maturity
- Opções: 3-5 opções
- Sinais de maturidade: Incluir contagens de estrelas, idade do projeto, tamanho do ecossistema quando relevante
- Recomendações: Condicionais ("Rec se X", "Rec se Y"), com peso para ferramentas testadas em batalha
- Justificativa: Parágrafo completo com sinais de maturidade e contexto do projeto
standard
- Opções: 2-4 opções
- Recomendações: Condicionais ("Rec se X", "Rec se Y")
- Justificativa: Parágrafo padrão fundamentando recomendação no contexto do projeto
minimal_decisive
- Opções: Máximo 2 opções
- Recomendações: Recomendação única e decisiva
- Justificativa: Breve (1-2 frases) </calibration_tiers>
<output_format> Retornar EXATAMENTE esta estrutura:
## {area_name}
| Opção | Prós | Contras | Complexidade | Recomendação |
|-------|------|---------|--------------|--------------|
| {opção} | {prós} | {contras} | {superfície + risco} | {rec condicional} |
**Justificativa:** {parágrafo fundamentando recomendação no contexto do projeto}
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.
- 7d ago First seen · 111 lines · 52 tokens per session scan A eeaafc047ec8
advisor-researcher is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 1,273 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.