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 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/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/cwinvestments/memstack/n8n-workflow-builder"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/n8n-workflow-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.02195 |
| Opus 5.5 | $0.00027 | $0.00878 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago Changed 98f9cc7da973
- 1mo 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 (425 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 2,195 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
multitask
Coordinate multi-part work through parallel subagents when two or more workstreams can proceed independently. Use for decomposable tasks where concurrency materially reduces the critical path; skip for trivial or tightly sequential work.
rtk-optimizer
Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then checks live state and existing authorization before proceeding.