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 yuchenbigpen1/normies --skill n8n-mcp-tools-expertgit clone --depth 1 https://github.com/yuchenbigpen1/normiesWrote 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/yuchenbigpen1/normies/n8n-mcp-tools-expert)<a href="https://agentmods.dev/skills/yuchenbigpen1/normies/n8n-mcp-tools-expert"><img src="https://agentmods.dev/badge/skills/yuchenbigpen1/normies/n8n-mcp-tools-expert/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/yuchenbigpen1/normies/n8n-mcp-tools-expert"><img src="https://agentmods.dev/badge/skills/yuchenbigpen1/normies/n8n-mcp-tools-expert.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.00059 | $0.04283 |
| Opus 5 | $0.00030 | $0.02142 |
| Sonnet 5 | $0.00012 | $0.00857 |
| Haiku 4.5 | $0.00006 | $0.00428 |
Grade A, and why
n8n-mcp-tools-expert 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 12d 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.
This is a copy
100% identical to n8n-mcp-tools-expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n MCP Tools Expert
Master guide for using n8n-mcp MCP server tools to build workflows.
Tool Categories
n8n-mcp provides tools organized into categories:
- Node Discovery → SEARCH_GUIDE.md
- Configuration Validation → VALIDATION_GUIDE.md
- Workflow Management → WORKFLOW_GUIDE.md
- Template Library - Search and deploy 2,700+ real workflows
- Documentation & Guides - Tool docs, AI agent guide, Code node guides
Quick Reference
Most Used Tools (by success rate)
| Tool | Use When | Speed |
|---|---|---|
search_nodes |
Finding nodes by keyword | <20ms |
get_node |
Understanding node operations (detail="standard") | <10ms |
validate_node |
Checking configurations (mode="full") | <100ms |
n8n_create_workflow |
Creating workflows | 100-500ms |
n8n_update_partial_workflow |
Editing workflows (MOST USED!) | 50-200ms |
validate_workflow |
Checking complete workflow | 100-500ms |
n8n_deploy_template |
Deploy template to n8n instance | 200-500ms |
Tool Selection Guide
Finding the Right Node
Workflow:
1. search_nodes({query: "keyword"})
2. get_node({nodeType: "nodes-base.name"})
3. [Optional] get_node({nodeType: "nodes-base.name", mode: "docs"})
Example:
// Step 1: Search
search_nodes({query: "slack"})
// Returns: nodes-base.slack
// Step 2: Get details
get_node({nodeType: "nodes-base.slack"})
// Returns: operations, properties, examples (standard detail)
// Step 3: Get readable documentation
get_node({nodeType: "nodes-base.slack", mode: "docs"})
// Returns: markdown documentation
Common pattern: search → get_node (18s average)
Validating Configuration
Workflow:
1. validate_node({nodeType, config: {}, mode: "minimal"}) - Check required fields
2. validate_node({nodeType, config, profile: "runtime"}) - Full validation
3. [Repeat] Fix errors, validate again
What ships with it
4 files 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.
- 12d ago First seen · 643 lines · 59 tokens per session scan A abb7737f1ef3
n8n-mcp-tools-expert is a skill published in the GitHub repository yuchenbigpen1/normies (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 4,283 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to n8n-mcp-tools-expert, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
[object Object]
Skill "[object Object]" from microsoft/apm, covering what this package does, getting started, available primitives and included workflows.
apm-usage
Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any apm CLI command.
frontend-state-management
SocialApp user frontend state management — TanStack Query, Zustand, IndexedDB persistence, cache invalidation, multi-account isolation.
dev-orchestrator
Full-stack development orchestrator -- always-on, 16 phases (0-15): read-docs -> understand -> architect -> pseudocode -> plan -> contract -> validate -> implement -> evaluate -> verify -> test -> goals -> review -> critic -> document -> report.
bot-reviewer
Review chat bot code (Telegram, Discord, Slack) for callback safety, state machines, rate limits, and production readiness.
silent-failure-hunter
Detects swallowed errors, empty catch blocks, log-and-forget patterns, and fallback masks that hide failures. Zero tolerance for silent failures. Severity-graded output with concrete fixes per language.