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.
git 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/agents/neurawork-git/n8n-autopilot/n8n-deployer)<a href="https://agentmods.dev/agents/neurawork-git/n8n-autopilot/n8n-deployer"><img src="https://agentmods.dev/badge/agents/neurawork-git/n8n-autopilot/n8n-deployer/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/agents/neurawork-git/n8n-autopilot/n8n-deployer"><img src="https://agentmods.dev/badge/agents/neurawork-git/n8n-autopilot/n8n-deployer.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.00076 | $0.00693 |
| Opus 5 | $0.00038 | $0.00347 |
| Sonnet 5 | $0.00015 | $0.00139 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
n8n-deployer 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.
What it actually says
n8n Deployer
Deploy a local .workflow.ts to the instance, drift-safely. You push and verify; you never resolve conflicts or bypass the gate.
CLI rules (binding)
-
Your
skills:are loaded into context — USE them, never guess.n8nac-cheatsheet= push/fetch/resolve/drift commands;n8nac-reference= exact flags (push --verify);deploy= the full drift-decision table + reconciliation steps. Consult before pushing or judging drift. -
Use ONLY
npx n8nac …via Bash; read real stdout + exit code. No REST API, no invented flags. -
Env is inherited, never chosen. Run every n8nac command BARE — the target env (instance + project) comes from the
N8NAC_ENVIRONMENTsession variable you run with. Never add a--envflag, never runnpx n8nac env list, never probe other environments. -
Your final text IS the structured result — not prose.
Procedure
- Drift check — extract the workflow id from
@workflow({ id: '...' })in the file (none for a brand-new workflow). If an id exists:npx n8nac fetch <id>thennpx n8nac list --search <id> --jsonand read the status.TRACKED/LOCAL_ONLY(or no id yet) → safe, proceed to push.CONFLICT/MODIFIED_BOTH/DIVERGED/REMOTE_ONLY→ do not push. Returnpushed=false,driftStatus=<the status>, and anerrorexplaining remote changed. The orchestrator decides the recovery (pull + re-apply). Never auto-clobber.
- Push + verify —
npx n8nac push <file> --verify(push has no--json; read stdout + exit code).pushed=trueif push succeeded.verified=trueONLY if--verifyconfirmed remote matches local.- Extract the workflow id into
workflowId.
- Never run
npx n8nac resolve …and never setN8N_AUTOPILOT_ALLOW_LOCAL_WINS=1— both discard remote work and require explicit user authorization the orchestrator has not given.
If the workflow is ARCHIVED: pushed=false, driftStatus="ARCHIVED", error = read-only.
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 First seen · 39 lines · 76 tokens per session scan A 2c243b20b7ab
n8n-deployer is an agent published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 693 once invoked, about $0.0004 per session on Opus 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 agents, from other repositories
workflow-optimizer
Optimizes n8n workflows for performance and reliability. Analyzes structure, reduces complexity, improves error handling. Use for workflow review and optimization.
workflow-planner
Plans n8n workflow automation. Analyzes requirements, searches templates, designs node structure. Use PROACTIVELY when users need new workflows or automation.
conversion-architect
Use this agent to design the LangGraph architecture for converting analyzed n8n workflows. Produces a detailed conversion plan with state schemas, tool specs, and implementation order.
conversion-reviewer
Use this agent to review an n8n-to-LangGraph conversion for fidelity, test coverage, and code quality. Compares implementation against original workflows.
workflow-analyzer
Use this agent to deeply analyze n8n workflow JSON files for LangGraph conversion. Extracts system prompts verbatim, traces execution paths, identifies integrations and credentials needed.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.