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 deploygit 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/deploy)<a href="https://agentmods.dev/skills/neurawork-git/n8n-autopilot/deploy"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/deploy/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/deploy"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/deploy.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.00054 | $0.02152 |
| Opus 5.5 | $0.00022 | $0.00861 |
| Sonnet 5.5 | $0.00011 | $0.00430 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
deploy 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Workflow
Push a local .workflow.ts to n8n via n8nac, verify remote state, run a live test.
Model-invocable, with a user gate on activation. The push itself is guarded fail-closed by the PreToolUse hooks (env-gate, push-gate for drift, push-lint-gate) and lands as a draft — the published version stays live. That is why Claude may run this skill when the user asks to deploy in plain words. Activation and the production test are the irreversible part: run step 8 only when the user explicitly asked for it (
--activate/--prodor "aktivieren" / "activate" in their request). Otherwise stop after step 7 and ask once whether to activate. (Before 5.6.2 the skill carrieddisable-model-invocation: true; CLAUDE.md routed plain-language deploy requests to it anyway, so they were refused.)
Steps
1. Resolve workflow
- File path (e.g.,
workflows/create-lead.workflow.ts) — use directly - Workflow name (e.g.,
create lead) — find matching.workflow.tsinworkflows/
If $ARGUMENTS is provided, use it. Otherwise, ask the user.
2. Validate before push (mandatory)
npx n8nac skills validate workflows/<name>.workflow.ts --strict --json
If validation fails → stop and report. Do not push with validation errors. For interpreting
the error (false-positives, expression vs schema errors, auto-sanitization, bulk fixes), consult the
companion n8n-architect skill's Common Mistakes — n8nac's raw validator messages are often terse.
2b. Expect the push-lint gate (runs inside push, fail-closed)
npx n8nac push is wrapped by a PreToolUse hook that compiles the file and refuses the push when
(1) a node type or typeVersion is missing on the running instance, (2) a top-level parameter does
not exist for the node's typeVersion (n8n ignores it silently), or (3) the design lint fails —
no error strategy on a top-level workflow with external calls, continueOnFail without a downstream
error check, unwired error output, orphan node, unbalanced expression, availableInMCP not true.
Read the BLOCK <rule> <node> <message> lines, fix the .workflow.ts, push again. Rules and
fix paths: docs/rules/gates.md. The bypass
(N8N_AUTOPILOT_SKIP_LINT=1) exists for the user, not for the agent.
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 Changed · +9 lines · +7 tokens per session 0238ec46a542
- 24d ago Changed · +11 lines f27c00961a1c
- 1mo ago First seen · 159 lines · 47 tokens per session scan A 6f8fd9d0a5b8
deploy is a skill published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 10d ago), licensed MIT. It adds 54 tokens to every session and 2,152 once invoked, about $0.0002 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-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-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-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-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled…