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/MN-Lizard-Team/aiyu-multi-agentWrote 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/rules/mn-lizard-team/aiyu-multi-agent/n8n-automation)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/n8n-automation"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/n8n-automation.svg" alt="Measured on agentmods" 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.00088 | $0.01412 |
| Opus 5 | $0.00044 | $0.00706 |
| Sonnet 5 | $0.00018 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
n8n-automation 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 4d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: n8n-automation
Cursor Agent-Requested Rule — invoke via
@n8n-automationor let the AI auto-select.
Skills: clean-code, api-patterns, bash-linux Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
n8n-automation| Skills:clean-code, api-patterns, bash-linux| Rules:GEMINI, api-design-rules, deployment-rules, performance-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- n8n workflow
- no-code/low-code integration
- ETL
- webhook automation
- business process automation
n8n Automation Specialist
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"If you do it more than twice, automate it. n8n is the glue between your systems."
n8n Architecture
Trigger Nodes (When something happens)
│
▼
Action Nodes (Do something)
│
▼
Logic Nodes (Control flow)
│
▼
Data Nodes (Transform/Store)
Workflow Patterns
Pattern 1: Webhook → Transform → API
[Webhook Trigger] → [Code Node] → [IF Node]
├── True → [HTTP Request] → [Slack Notify]
└── False → [Slack Notify Rejection]
Pattern 2: Scheduled ETL
[Cron Trigger] → [HTTP Request] → [Set Node] → [Function Node] → [Split Batches] → [Postgres] → [Slack]
Pattern 3: Approval Workflow
[Form Trigger] → [IF Needs Approval?]
├── Yes → [Create Doc] → [Email Approver] → [Wait Webhook]
│ └── [IF Approved?] → [Yes: Execute+Notify] / [No: Rejection]
└── No → [Auto-execute] → [Notify]
Best Practices
Node Naming
"Trigger — Stripe Payment Success"
"Validate — Payload Check"
"Action — Create Salesforce Lead"
"Action — Send Welcome Email"
Error Handling
- Error Workflow: Global error capture, alert to Slack/PagerDuty
- Continue on Fail: Non-critical nodes skip on error
- Retry: 3 retries with exponential backoff for API calls
- Fallback: Default values when data missing
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.
- 4d ago First seen · 180 lines · 88 tokens per session scan A 6bb3281a9790
n8n-automation is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,412 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.