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 anatolykoptev/n8n-mcp-agent --skill n8n-diagnosticsgit clone --depth 1 https://github.com/anatolykoptev/n8n-mcp-agentWrote 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/anatolykoptev/n8n-mcp-agent/n8n-diagnostics)<a href="https://agentmods.dev/skills/anatolykoptev/n8n-mcp-agent/n8n-diagnostics"><img src="https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/n8n-diagnostics/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/anatolykoptev/n8n-mcp-agent/n8n-diagnostics"><img src="https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/n8n-diagnostics.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.00041 | $0.01211 |
| Opus 5 | $0.00020 | $0.00606 |
| Sonnet 5 | $0.00008 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
n8n-diagnostics 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 10d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n Diagnostics Skill
When to Use This Skill
Use n8n-diagnostics when:
- Workflow executions fail or behave unexpectedly
- n8n service is unhealthy or unresponsive
- Need to analyze logs for error patterns
- Debugging connectivity or credential issues
- Performance problems in n8n instance
Available MCP Tools
n8n-diagnose
Primary diagnostic tool. Runs comprehensive health checks and returns actionable recommendations.
Input: { clientId, workflowId?, verbose? }
Output: { status, issues[], recommendations[] }
Use when:
- Quick overview of n8n health needed
- Specific workflow is failing
- Need to identify root cause of issues
n8n-analyze-logs
Parses n8n logs and extracts error patterns, warnings, and anomalies.
Input: { clientId, lines?, since?, filter? }
Output: { errors[], warnings[], patterns[] }
Use when:
- Need to analyze historical issues
- Looking for recurring error patterns
- Debugging intermittent failures
n8n-health-check
Lightweight health check for service availability and basic metrics.
Input: { clientId }
Output: { healthy, latency, version, uptime }
Use when:
- Quick availability check needed
- Monitoring service status
- Before running workflows
Decision Tree
Problem reported
│
├─► "n8n is down/unresponsive"
│ └─► n8n-health-check
│ │
│ ├─► healthy=false → Check Docker/service status
│ └─► healthy=true → n8n-diagnose for deeper issues
│
├─► "Workflow X is failing"
│ └─► n8n-diagnose { workflowId: X }
│ │
│ ├─► Credential error → Re-configure credentials
│ ├─► Connection error → Check dependent services
│ └─► Logic error → Review workflow nodes
│
├─► "Something seems wrong, not sure what"
│ └─► n8n-analyze-logs { lines: 500 }
│ │
│ └─► Review patterns → n8n-diagnose for specific issues
│
└─► "Need to debug specific timeframe"
└─► n8n-analyze-logs { since: "2h" }
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 172 lines · 41 tokens per session scan A 7e36ee8406a7
n8n-diagnostics is a skill published in the GitHub repository anatolykoptev/n8n-mcp-agent (0 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,211 once invoked, about $0.0002 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 skills, from other repositories
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.