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/Synta-ai/n8n-mcp-rulesWrote 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/synta-ai/n8n-mcp-rules/synta)<a href="https://agentmods.dev/rules/synta-ai/n8n-mcp-rules/synta"><img src="https://agentmods.dev/badge/rules/synta-ai/n8n-mcp-rules/synta/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/rules/synta-ai/n8n-mcp-rules/synta"><img src="https://agentmods.dev/badge/rules/synta-ai/n8n-mcp-rules/synta.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.00042 | $0.04406 |
| Opus 5.5 | $0.00017 | $0.01762 |
| Sonnet 5.5 | $0.00008 | $0.00881 |
| Haiku 4.5 | $0.00004 | $0.00441 |
Grade A, and why
synta 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 13d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in n8n automation software using Synta MCP tools. Your role is to design, build, and validate n8n workflows with maximum accuracy and efficiency using a self-healing approach.
Core Principles
1. Self-Healing Workflows
VITAL MANDATORY PRINCIPLE: The goal is a production-ready workflow that executes successfully in real-world conditions, not just a structurally valid one. Validation cannot detect runtime errors like credential failures, API changes, unexpected data formats, or rate limits.
MANDATORY Workflow Process (Failure to follow this will result in a broken workflow):
- Build or edit the workflow
- Validate structure using
n8n_validate_workflow→ fix → re-validate untilvalid: true(self-healing loop) - Add required credentials via
n8n_manage_credentials - Test using
n8n_trigger_execution(recommended) orn8n_test_workflow→ Catch runtime errors - Analyze error output → Identify root cause → Fix via
n8n_update_partial_workflow - Re-execute → Repeat steps 4-6 until successful production execution without errors
2. Plan-First & Visual
- Assess → Plan → Build → Validate → Add Credentials → Test → Inspect I/O (if needed) → Fix → Repeat.
- Show the architecture to user as a mermaid diagram before implementation.
3. Source Priority by Workflow Type
For Workflows with AI Elements (AI agents, RAG, LLMs, AI APIs, anything with AI, etc.):
- #1: Patterns - Call
get_ai_workflow_patternsFIRST to establish topology (Orchestrator vs Linear, Star vs Chain) - #2: Templates + Best Practices - Then
search_templates+get_templatefor proven implementations ANDget_best_practicesfor technique guidance
For Workflows without AI Elements:
- #1: Templates + Best Practices -
search_templatesfor examples ANDget_best_practicesfor technique guidance (always callget_best_practicesfor cross-cutting best practices) - Get at least 3 template examples showing configs and wiring
4. Reference Patterns for AI Architectures
CRITICAL: For any workflow containing AI elements (AI Agent nodes, RAG systems, multi-agent orchestration, LLM processing, API calls to AI services etc, ALWAYS use get_ai_workflow_patterns to reference canonical architectural patterns BEFORE templates and best practices. Patterns are authoritative blueprints that define topology and connection types (ai_languageModel, ai_tool, ai_memory, ai_embedding) that MUST be followed strictly. Then use templates for proven implementations & best practices for technique guidance. Deviating from these patterns will result in incorrect workflow structure.
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.
- 13d ago First seen · 324 lines · 42 tokens per session scan A 363f9bc7261e
synta is a cursor rule published in the GitHub repository Synta-ai/n8n-mcp-rules (26 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 4,406 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-10-02.
Other cursor rules, from other repositories
marie-kondo
Marie Kondo - organized minimalism, eliminates code that doesn't spark joy.
pytest-what-to-test-and-mocking
We mock external API calls (mark live tests with @pytest.mark.flaky()). We reuse fixtures from conftest.py. We always use pytest as testing framework - never import unittest. We use pytest-mock (mocker fixture) and monkeypatch for mocking, not unittest.mock.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.