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 komunite/kalfa --skill n8n-workflowgit clone --depth 1 https://github.com/komunite/kalfaWrote 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/komunite/kalfa/n8n-workflow)<a href="https://agentmods.dev/skills/komunite/kalfa/n8n-workflow"><img src="https://agentmods.dev/badge/skills/komunite/kalfa/n8n-workflow.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.00018 | $0.01410 |
| Opus 5 | $0.00009 | $0.00705 |
| Sonnet 5 | $0.00004 | $0.00282 |
| Haiku 4.5 | $0.00002 | $0.00141 |
Grade A, and why
n8n-workflow 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.
This is a copy
84% identical to agent-evaluation — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
N8n Workflow
Amaç
Eyleme dönüştürülebilir, ölçülebilir sonuçlar sunan kapsamlı bir n8n workflow tasarlayın ve belgeleyin. Bu beceri, her seferinde profesyonel düzeyde çıktı sağlayan, kalite doğrulamalı yapılandırılmış bir süreç sunar.
Kategori: Yapay Zeka ve Otomasyon
Girdiler
Zorunlu
- Hedef: Bu çıktı ile neyi başarmak istiyorsunuz
- Bağlam: İlgili arka plan bilgileri
İsteğe Bağlı
- Kısıtlamalar: Dikkate alınması gereken sınırlamalar veya gereksinimler
- Mevcut Çalışma: Üzerine inşa edilecek önceki belgeler veya veriler
Sistem Bağlamı
Başlamadan önce:
- Mevcut proje bağlamı ve öncelikleri için
memory.md'yi oku - İlgili öğrenilmiş kurallar veya kısıtlamalar için
knowledge-base.md'yi kontrol et - Projedeki mevcut ilgili belgeleri gözden geçir
- Bu çıktı ile ilgili
.claude/workspace/TaskBoard.md'deki aktif görevleri not et
Süreç
Adım 1: Bağlam ve Araştırma
- Projedeki mevcut n8n workflow belgelerini gözden geçir
- İlgili öğrenilmiş kurallar veya kısıtlamalar için
knowledge-base.md'yi kontrol et - Mevcut proje bağlamı ve öncelikleri için
memory.md'yi kontrol et - Kilit paydaşları ve gereksinimlerini belirle
- En uygun çerçeveyi seç: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design
Adım 2: Analiz ve Çerçeve Uygulaması
- n8n workflow yapılandırmak için seçilen çerçeveyi uygula
- Boşlukları, fırsatları ve riskleri belirle
- Başarı metriklerini tanımla: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation
- Varsayımları ve bağımlılıkları belgele
- Yaklaşımı sektör en iyi uygulamalarına göre doğrula
Adım 3: Çıktıyı Oluştur
- n8n workflow aşağıdaki çıktı formatını kullanarak yapılandır
- Genel tavsiyeler değil, spesifik ve eyleme dönüştürülebilir öneriler ekle
- Uygulanabilir yerlerde somut rakamlar, zaman çizelgeleri ve kıyaslamalar ekle
- Tutarlılık için mevcut proje belgeleriyle çapraz referans yap
- Her bölümün değer kattığından emin ol — dolgu içeriği çıkar
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 · 133 lines · 18 tokens per session scan A 369028a7f444
n8n-workflow is a skill published in the GitHub repository komunite/kalfa (244 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,410 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to agent-evaluation, differing in 54 lines, and is treated as a copy.
Other skills, from other repositories
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…
Product Strategy
A comprehensive skill for product strategy — covering frameworks, opportunity sizing, prioritization, roadmap building, OKRs, and stakeholder management. From early-stage discovery to mature product org execution.
handover-admin
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".
project-context-setup
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…
website-clone-final-report
Generate a website-clone closure report comparing baseline analysis, builder metadata, planned tasks, and implemented results. Use after a completed rebuild. Don't use for live audits, ongoing monitoring, implementation, or speculative metrics.
to-tickets
A method for turning a plan, specification, or conversation into small work tickets that each deliver a complete, testable slice of functionality. Each ticket records which other tickets must be finished first.