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.
npx skills add zihin-ai/zihin-mcp --skill zihin-diagnosticogit clone --depth 1 https://github.com/zihin-ai/zihin-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/skills/zihin-ai/zihin-mcp/zihin-diagnostico)<a href="https://agentmods.dev/skills/zihin-ai/zihin-mcp/zihin-diagnostico"><img src="https://agentmods.dev/badge/skills/zihin-ai/zihin-mcp/zihin-diagnostico/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/skills/zihin-ai/zihin-mcp/zihin-diagnostico"><img src="https://agentmods.dev/badge/skills/zihin-ai/zihin-mcp/zihin-diagnostico.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.00061 | $0.01290 |
| Opus 5.5 | $0.00024 | $0.00516 |
| Sonnet 5.5 | $0.00012 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
zihin-diagnostico 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 23d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnóstico de agentes
Comece SEMPRE pelo sintoma, não pela ferramenta. Ordem de investigação:
1. Visão geral do agente
get_agent_metrics (period 1d/7d/30d) — calls, errors, success_rate, tokens, custo, latência p50/p95 (agregado em SQL, sem cap de linhas), uso de tools e sessões recentes. Se tools.sample_truncated: true, os agregados de tools refletem a amostra das últimas 2000 chamadas, não o período inteiro.
Interpretação rápida:
- errors altos + success_rate baixo → veja o passo 2 (tools) e 5 (infra).
- custo alto → cheque modelo em uso (
get_agent), fallback_chain e volume de sessões; considere teto (zihin://skills/governanca-e-operacao). - p95 alto → tools lentas (passo 2) ou modelo pesado.
2. Tools resolvendo?
list_agent_tools — cada tool aparece com status resolved ou error.
Assinatura clássica: usuário final recebe "Tool not found", mas a telemetria mostra a execução como sucesso → o MCP server externo está inativo/erro e as tools sumiram do runtime. Correção: test_mcp_server (ping + auth) → corrigir endpoint/credencial se preciso → invalidate_mcp_cache (cache tem TTL 5 min; invalidar força reload).
Confirme a hipótese com get_execution_diagnostics: compare tools_loaded (contagem) e tools_loaded_names do turno bom com os do turno ruim. Contagem oscilando entre turnos = churn de superfície (MCP externo em flap), não bug do agente. Agente em modo serve de superfície (snapshot A4) mostra em tools_loaded_names exatamente o que o modelo viu — uma tool nova que não aparece ali está fora do snapshot ativo (para incluí-la, invalide a superfície — invalidate_mcp_cache ou a mudança de schema/CSP já fazem isso).
Para api_config com erro: validate_agent_schemas aponta o schema quebrado; lembre da regra endpoint.name == tool_definition.name. Agente que responde "ferramenta indisponível" com tool_call_logs mostrando not a valid tool: a mesma tool aponta em surface.cited_outside — uma skill/persona ensina uma tool que a CSP bloqueia (blocked_by_csp) ou que o servidor não oferece mais (not_in_surface).
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.
- 23d ago Changed · +5 lines 3aae0a7cecac
- 1mo ago First seen · 55 lines · 61 tokens per session scan A f2c095520c36
zihin-diagnostico is a skill published in the GitHub repository zihin-ai/zihin-mcp (0 stars, last pushed 23d ago), licensed MIT. It adds 61 tokens to every session and 1,290 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.