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 agentmods add skills/cwinvestments/memstack/n8n-workflow-buildernpx skills add cwinvestments/memstack --skill n8n-workflow-buildergit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/n8n-workflow-builder)<a href="https://agentmods.dev/skills/cwinvestments/memstack/n8n-workflow-builder"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/n8n-workflow-builder.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 | $0.00068 | $0.02195 |
| Opus 5 | $0.00034 | $0.01097 |
| Sonnet 5 | $0.00014 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
memstack-automation-n8n-workflow-builder 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 today.
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n Workflow Builder: Designing automation workflow...
Designs visual n8n workflows with trigger selection, node mapping, data transformations, error handling, and webhook integration.
Activation
When this skill activates, output:
n8n Workflow Builder: Designing automation workflow...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "n8n workflow", "build a workflow", "automation workflow" | ACTIVE |
| User says "connect services" or wants visual automation | ACTIVE |
| User wants to automate a multi-step process with n8n | ACTIVE |
| User needs a standalone webhook endpoint | DORMANT: use Webhook Designer |
| User needs a cron/scheduled job without n8n | DORMANT: use Cron Scheduler |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "One giant workflow" | Workflows over 20 nodes become unmaintainable. Split into sub-workflows with triggers. |
| "No error handling" | Silent failures mean lost data. Every workflow needs an Error Trigger node. |
| "Hardcoded credentials" | Use n8n's credential store, never paste API keys into HTTP Request nodes. |
| "Skip testing with real data" | Test with production-like payloads. Dummy data hides type mismatches and missing fields. |
| "Poll when you can webhook" | Polling wastes resources. If the service supports webhooks, use the Webhook trigger instead. |
Protocol
Step 1: Gather Workflow Requirements
If the user hasn't provided details, ask:
- Trigger: what starts the workflow? (webhook, schedule, app event, manual)
- Input: what data comes in? (payload shape, source service)
- Actions: what should happen step-by-step?
- Output: where does the result go? (database, API, email, Slack, file)
- Error handling: what happens if a step fails?
- Frequency: how often does this run? (per event, hourly, daily)
Step 2: Select Trigger Node
| Trigger Type | n8n Node | When to Use |
|---|---|---|
| Incoming webhook | Webhook | External service sends data to you |
| Schedule | Schedule Trigger | Run at fixed intervals (cron) |
| App event | [App] Trigger | Slack message, GitHub PR, Stripe payment, etc. |
| Manual | Manual Trigger | Testing or on-demand execution |
| Email Trigger (IMAP) | React to incoming emails | |
| File change | Local File Trigger | Watch a directory for new files |
| Another workflow | Execute Workflow Trigger | Sub-workflow called by parent |
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.
- today Changed 98f9cc7da973
- 4d ago First seen · 273 lines · 68 tokens per session scan A b47152652a8c
memstack-automation-n8n-workflow-builder is a skill published in the GitHub repository cwinvestments/memstack (419 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 2,195 once invoked, about $0.0003 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 skills, from other repositories
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…