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 neurawork-git/n8n-autopilot --skill n8nac-cheatsheetgit clone --depth 1 https://github.com/neurawork-git/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/n8nac-cheatsheet)<a href="https://agentmods.dev/skills/neurawork-git/n8n-autopilot/n8nac-cheatsheet"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/n8nac-cheatsheet/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/n8nac-cheatsheet"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/n8nac-cheatsheet.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.00086 | $0.03746 |
| Opus 5.5 | $0.00034 | $0.01498 |
| Sonnet 5.5 | $0.00017 | $0.00749 |
| Haiku 4.5 | $0.00009 | $0.00375 |
Grade A, and why
n8nac-cheatsheet 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 26d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8nac Cheat-Sheet
Source-of-truth for "what command do I run for X?" If your task matches a row, run the exact command shown — do not paraphrase, do not invent flags, do not run --help. If no row matches, fall back to n8nac-reference for the full help tree.
All commands below assume
npx n8nac …and a workspace bound to an n8n instance (workspace status: bound). Replace<id>,<name>,<path>with concrete values.
Workspace & Setup
| User intent | Command |
|---|---|
| First-time setup (connect to existing n8n) | npx n8nac env add <name> --base-url "$N8N_API_URL" --workflows-path workflows then printf "%s" "$N8N_API_KEY" | npx n8nac env auth set <name> --api-key-stdin then npx n8nac env use <name> |
| List supported setup modes | npx n8nac setup-modes |
| Show effective workspace context (active project, instance, sync folder) | npx n8nac workspace status --json |
| Bind instance + set sync folder (new env) | npx n8nac env add <name> --base-url <url> --workflows-path workflows |
| Switch active project on an environment | npx n8nac env update <env> --project-name "<name>" or --project-id "<id>" |
| Set workflow sync folder on an existing env | npx n8nac env update <env> --workflows-path <relativePath> |
Multi-Environment (multiple n8n instances per repo)
| User intent | Command |
|---|---|
| List configured environments | npx n8nac env list --json |
| Show active environment + auth state | npx n8nac env status --json |
| Add a new environment | npx n8nac env add <name> --base-url <url> --workflows-path workflows |
| Switch active environment | npx n8nac env use <name> (alias: env pin) |
| Store API key for an environment | printf "%s" "$N8N_API_KEY" | npx n8nac env auth set <name> --api-key-stdin |
| Remove the stored API key of ONE environment (n8nac ≥ 2.5) | npx n8nac env auth clear <name> |
| Update any env property (URL / project / sync folder / name) | npx n8nac env update <name-or-id> --base-url <url> (swap flag as needed) |
| Target one command at a non-active env | npx n8nac --env <name> <command> (root flag) |
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.
- 26d ago Changed · +42 lines 95e9dc99ef7d
- 1mo ago First seen · 155 lines · 86 tokens per session scan A 1aedd3270158
n8nac-cheatsheet is a skill published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 12d ago), licensed MIT. It adds 86 tokens to every session and 3,746 once invoked, about $0.0003 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-30.
Other skills, from other repositories
n8n
Use when the user wants to build, debug, or extend an n8n workflow - generating workflow JSON from a description, scaffolding a custom TypeScript node, building an AI agent (LangChain cluster), iterating over items, writing Code-node JS, linting an existing workflow, diagnosing a failed execution, or driving a live…
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-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-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 — including the native nodes that replace Code (Summarize, Aggregate, Split Out…