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 Impertio-Studio/n8n-Claude-Skill-Package --skill n8n-impl-workflow-designgit clone --depth 1 https://github.com/Impertio-Studio/n8n-Claude-Skill-PackageWrote 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/impertio-studio/n8n-claude-skill-package/n8n-impl-workflow-design)<a href="https://agentmods.dev/skills/impertio-studio/n8n-claude-skill-package/n8n-impl-workflow-design"><img src="https://agentmods.dev/badge/skills/impertio-studio/n8n-claude-skill-package/n8n-impl-workflow-design/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/impertio-studio/n8n-claude-skill-package/n8n-impl-workflow-design"><img src="https://agentmods.dev/badge/skills/impertio-studio/n8n-claude-skill-package/n8n-impl-workflow-design.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.00141 | $0.02747 |
| Opus 5 | $0.00071 | $0.01373 |
| Sonnet 5 | $0.00028 | $0.00549 |
| Haiku 4.5 | $0.00014 | $0.00275 |
Grade A, and why
n8n-impl-workflow-design 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 12d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n Workflow Design Patterns
Quick Reference
| Pattern | Primary Node | When to Use |
|---|---|---|
| Sub-workflow | Execute Workflow | Reusable logic, separation of concerns, >20 nodes |
| Error handling | Error Trigger + Stop And Error | Centralized failure notification and recovery |
| Branching | IF / Switch | Conditional routing based on data values |
| Merging | Merge | Combining data from parallel branches |
| Looping | Loop Over Items | Batch processing, rate-limited API calls |
| Wait/Resume | Wait | Human approval, external callback, timed delay |
| Scheduling | Schedule Trigger | Recurring automated execution |
Decision Tree: Which Pattern Do I Need?
Need to reuse logic across workflows?
├─ YES → Sub-workflow (Execute Workflow node)
└─ NO
Need to handle failures gracefully?
├─ YES → Is it a single node that might fail?
│ ├─ YES → continueOnFail + IF node to check $json.error
│ └─ NO → Error workflow (Error Trigger node)
└─ NO
Need to route data conditionally?
├─ YES → Two outcomes? → IF node
│ Multiple outcomes? → Switch node
└─ NO
Need to combine data from multiple sources?
├─ YES → Merge node (choose mode based on use case)
└─ NO
Need to process items in batches?
├─ YES → Loop Over Items node
└─ NO
Need to pause and wait?
├─ YES → Wait node (time, webhook, or form resume)
└─ NO → Schedule Trigger for recurring execution
1. Sub-Workflow Patterns
Execute Workflow Node
ALWAYS use the Execute Workflow node to call another workflow as a sub-workflow. NEVER duplicate logic across workflows.
Parameter passing:
- The calling workflow sends input items to the sub-workflow
- The sub-workflow receives items at its trigger node
- The sub-workflow returns its final output back to the caller
Caller policy (callerPolicy in workflow settings):
workflowsFromSameOwner— Only workflows owned by the same user (DEFAULT)workflowsFromAList— Only workflow IDs listed incallerIdsany— Any workflow can call this sub-workflownone— NEVER allow this workflow to be called as a sub-workflow
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 278 lines · 141 tokens per session scan A ab9336c55e8f
n8n-impl-workflow-design is a skill published in the GitHub repository Impertio-Studio/n8n-Claude-Skill-Package (3 stars, last pushed 2mo ago), licensed MIT. It adds 141 tokens to every session and 2,747 once invoked, about $0.0007 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-31.
Other skills, from other repositories
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
django-storages-s3
Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.