Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add neurawork-git/n8n-autopilot/plugin install n8n-autopilotWrote 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/neurawork-git/n8n-autopilot/check-mcps)<a href="https://agentmods.dev/skills/neurawork-git/n8n-autopilot/check-mcps"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/check-mcps/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/neurawork-git/n8n-autopilot/check-mcps"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/check-mcps.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.00064 | $0.00761 |
| Opus 5 | $0.00032 | $0.00380 |
| Sonnet 5 | $0.00013 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade B, and why
check-mcps scanned grade B with 1 finding 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -q '"n8n-as-code@n8nac-marketplace": true' "$HOME/.claude/settings.json" && \ How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check n8n-autopilot Setup
n8n-autopilot is CLI-only (npx n8nac …). There is no MCP server entry for this plugin — the mcp__n8n-as-code__* namespace seen in older docs was an upstream assumption that never landed (the npm n8nac mcp entry-point is broken and Etienne's companion plugin ships skill knowledge, not an MCP server).
This skill verifies the actually-required layers.
Step 1 — n8nac CLI reachable
npx n8nac --version 2>&1
Expect 2.2.0 or higher. Anything below is unsupported.
Step 2 — Full health check via setup-check.sh
bash "$CLAUDE_PLUGIN_ROOT/scripts/setup-check.sh" 2>&1
($CLAUDE_PLUGIN_ROOT is set by Claude Code when running plugin commands — no manual path needed.)
Inspect the output. The script checks, in order:
npxavailable- n8nac CLI version vs minimum/reference
- n8nac workspace bound (
workspace status --jsonreturns env config) - n8n API reachable (host pulled from the workspace status JSON)
- Companion plugin
n8n-as-code@n8nac-marketplaceenabled (warns if missing — the companion'sn8n-architectskill is the primary source of n8n authoring knowledge) - Community-node schema coverage
- Inventory freshness (informational)
Step 3 — Companion plugin (n8n-as-code) enabled
grep -q '"n8n-as-code@n8nac-marketplace": true' "$HOME/.claude/settings.json" && \
echo "OK: n8n-as-code companion enabled" || \
echo "WARN: n8n-as-code companion not enabled — install it for best UX:
claude plugin marketplace add EtienneLescot/n8n-as-code
claude plugin install n8n-as-code@n8nac-marketplace"
Step 4 — Project visibility
node "$CLAUDE_PLUGIN_ROOT/skills/find-project/scripts/list.js"
Prints the workspace-pinned project plus every project derivable from credential ownership. Surface the table to the user — multi-project blindness (referencing creds from the wrong project) is the most common cause of "workflow pushes but fails at runtime".
Step 5 — Report
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.
- 11d ago First seen · 74 lines · 64 tokens per session scan B daf2ca913240
check-mcps is a skill published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 761 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
n8n-mcp-tools-expert
Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, organizing workflows into folders, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats…
n8n-agents
Design n8n AI agents the right way. Use when building or editing any @n8n/n8n-nodes-langchain. AI node — an AI Agent, LLM chain, Text Classifier, or Information Extractor — and whenever the user mentions AI agents, LLM with tools, tool calling, $fromAI, system prompts, agent memory, sessionId, structured/JSON output…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
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-expression-syntax
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from…
n8n-node-configuration
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between getnode detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are…