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 gaelic-ghost/socket --skill design-n8n-agent-workflowgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/design-n8n-agent-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/design-n8n-agent-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/design-n8n-agent-workflow/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/gaelic-ghost/socket/design-n8n-agent-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/design-n8n-agent-workflow.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.00037 | $0.00422 |
| Opus 5.5 | $0.00015 | $0.00169 |
| Sonnet 5.5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
design-n8n-agent-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 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.
What it actually says
Design n8n Agent Workflow
Use this skill when n8n is the right visual, trigger-driven integration surface. It does not turn n8n into a default durable multi-agent runtime.
Source Check
- n8n hosting: https://docs.n8n.io/hosting/
- n8n and Ollama: https://n8n.io/integrations/ollama/
- Ollama: https://ollama.com/
Workflow
- Map trigger, deterministic transforms/routes, external reads, model step, draft output, and any external write separately.
- Select credentials/storage ownership, webhook exposure, retry policy, idempotency key, concurrency limit, and failed-run record before connecting an AI node.
- Treat the local model as one bounded node: prove structured output, tool compatibility when used, no-call behavior, malformed result recovery, and the exact model/server combination before exposing a write node.
- Keep source data minimised and trace/log retention explicit. Do not put secrets in workflow exports or prompts.
- Leave write nodes disabled or draft-only until
auto-with-escalationnames the recipient, action, payload evidence, and approval event. - Export a testable workflow fixture and verify happy path, duplicate event, failed model response, credential failure, rejected approval, and recovery.
Output Shape
Return trigger, node graph, credentials, idempotency/retry behavior, model contract, draft artifact, approval event, and recovery evidence.
Guardrails
- Prefer deterministic n8n nodes over agent planning whenever the route is known.
- Do not expose a self-hosted instance publicly without an explicit deployment and authentication decision.
- Do not claim a local model is reliable for tool use without a capability gate.
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 First seen · 46 lines · 37 tokens per session scan A 3b04a5807fec
design-n8n-agent-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 422 once invoked, about $0.0001 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-31.
Other skills, from other repositories
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…
pipeline-auto
Use when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
fast-pipeline
Use when the user wants a feature built quickly with low token cost and few interruptions, approves a spec once, and says no automated tests should be written because they will test it manually — "fast pipeline", "go fast, no tests, I'll test it myself", "don't keep asking me". Not for a run that should write or keep…