n8n-skills is a collection of Claude Code skills and hooks that guide AI assistants in creating, validating, and deploying n8n workflows through the n8n-mcp server. Developers use it to automate workflow construction, configure nodes and expressions, resolve validation errors, and operate self-hosted n8n. The catalogue entries are its skills, hooks, plugins, and instruction.
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 czlonkowski/n8n-skills --skill n8n-multi-instancegit clone --depth 1 https://github.com/czlonkowski/n8n-skillsWrote 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/czlonkowski/n8n-skills/n8n-multi-instance)<a href="https://agentmods.dev/skills/czlonkowski/n8n-skills/n8n-multi-instance"><img src="https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/n8n-multi-instance/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/czlonkowski/n8n-skills/n8n-multi-instance"><img src="https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/n8n-multi-instance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00181 | $0.03169 |
| Opus 5 | $0.00090 | $0.01584 |
| Sonnet 5 | $0.00036 | $0.00634 |
| Haiku 4.5 | $0.00018 | $0.00317 |
Grade A, and why
n8n-multi-instance 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 9d 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-multi-instance — 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with multiple n8n instances over MCP
When the n8n_instances tool is available, the user has multi-instance mode on: one MCP
connection can reach several n8n instances (e.g. prod, staging, or one per client/team).
Every other n8n tool (n8n_get_workflow, n8n_list_workflows, n8n_update_partial_workflow,
n8n_manage_datatable, n8n_manage_credentials, n8n_executions, n8n_test_workflow, …) runs
against whichever instance this session is currently targeting. There is no per-call instance
argument: you change the target only by switching. Target the wrong instance and a read returns the
wrong data and a write lands in the wrong place — usually with no error (the one exception is an
ambiguous credential write, which fails closed; see below). So target deliberately.
If the n8n_instances tool is not present, the account is single-instance: ignore this skill
and use the n8n tools directly.
Golden rules
Six rules. Each prevents a class of silent misroute.
- Discover first. Call
n8n_instances({mode:"list"})before acting so you know the instance names and which one iscurrent. - Switch by name to your target before doing work on a non-default instance:
n8n_instances({mode:"switch", name:"<instance name>"}). The match is case-insensitive. - Switch in its own turn. Never put a
switchand a dependent operation in the same parallel tool-call batch. Calls in one batch have no guaranteed order, so the dependent call can be resolved against the previous instance before the switch's session state is visible. Switch, let it return, then operate. - Verify before high-stakes ops. Immediately before creating/updating/deleting credentials
(and before destructive workflow edits), confirm
currentis the instance you intend — primary check isn8n_instances({mode:"list"}). The system fail-closes only the ambiguous credential case (rule 6); an explicit switch to the wrong instance still writes there silently, so this check is on you. - An unexpected
NOT_FOUNDis almost always a wrong-instance misroute, not a deletion. Don't recreate the object. Re-check the current instance and retry (see Recovery). - On
INSTANCE_AMBIGUOUS, switch on this session, then retry. The system is refusing to write a secret because this session never picked a target itself. Comply — runswitchhere to confirm the instance, then retry the write. Don't work around it or retry blindly.
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.
- 9d ago First seen · 189 lines · 181 tokens per session scan A 1995cb03cb89
n8n-multi-instance is a skill published in the GitHub repository czlonkowski/n8n-skills (6,205 stars, last pushed 6d ago), licensed MIT. It adds 181 tokens to every session and 3,169 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to n8n-multi-instance, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
build-workflow
Full 3-phase pipeline (Research → Write+Validate → Deploy+Test) for shipping an n8n workflow end-to-end. Wraps Etienne's n8n-as-code:n8n-architect skill for schema research + authoring, adds repo-scoped orchestration — community-template lookup, validate-push-test loop, mcpTrigger publish gate, execution inspection…
build-stack-v2
EXPERIMENTAL deterministic builder for a whole n8n workflow STACK (multiple sub-workflows wired via Execute Workflow), JS-orchestrated. Takes a PRP-style end-to-end use case, decomposes it into sub-workflows along known rules, fixes the handover contracts between them, documents the architecture (mermaid) in one…
build-workflow-v2
EXPERIMENTAL deterministic variant of build-workflow + deploy, JS-orchestrated. Two modes: GREENFIELD (new workflow) and EDIT (change an existing one). Phase ordering, gate-checks (validate / drift-safe push --verify), and fix-loop limits are enforced by a Claude Code JS Workflow script instead of prose — gates become…
deploy
Push a local .workflow.ts to n8n, verify remote state, and live-test (test URL by default; --activate --prod runs production test). Side-effecting — only invoked explicitly via /deploy.
n8n-code-javascript
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
n8n-orchestration-patterns
Fan-out / fan-in, parallel sub-workflow execution, and batch-orchestrator patterns in n8n. Use when a workflow processes a LIST in parallel, calls sub-workflows, needs faster wall-clock on many items, has a webhook that would otherwise block for minutes, or asks "how do I run sub-workflows in parallel / fan out / fan…