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/gaelic-ghost/socket/design-n8n-agent-workflownpx 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.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.00037 | $0.00422 |
| Opus 5 | $0.00018 | $0.00211 |
| Sonnet 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 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.
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.
- 4d 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 9d ago), licensed Apache-2.0. It adds 37 tokens to every session and 422 once invoked, about $0.0002 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
pipeline
Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…
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…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…
ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…
ai-research-analyst
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a…
implement-factory
Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.