Borrowing it
Nothing to install: this file belongs to yogasw/wick. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yogasw/wick/master/.claude/skills/workflow-node-module/SKILL.mdgit clone --depth 1 https://github.com/yogasw/wickWrote 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/yogasw/wick/workflow-node-module)<a href="https://agentmods.dev/skills/yogasw/wick/workflow-node-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/workflow-node-module/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/yogasw/wick/workflow-node-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/workflow-node-module.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.00132 | $0.08418 |
| Opus 5.5 | $0.00053 | $0.03367 |
| Sonnet 5.5 | $0.00026 | $0.01684 |
| Haiku 4.5 | $0.00013 | $0.00842 |
Grade A, and why
workflow-node-module 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 2mo 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 — 619 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Node Module — wick core
Activate this skill whenever the user touches a workflow node type — creating, improving, fixing, or adding fields. When editing an existing node, audit it against the rules below and bring it up to spec as part of the change.
Mental model
A node has two halves that share one schema:
| Half | Lives in | Touches |
|---|---|---|
| Engine (executor) | internal/agents/workflow/nodes/<type>.go |
runtime — receives workflow.Node, returns NodeOutput |
| UI plugin module (palette + inspector) | internal/tools/agents/workflow/nodes/<type>/ |
canvas — palette entry, drawflow codec, inspector partial, JS module |
The shared schema struct (exported type, e.g. HTTPSchema) lives in the engine package and is reflected by both:
- engine
Descriptor().Schema→integration.StructSchema(HTTPSchema{})→ MCPworkflow_node_types - UI inspector partial →
entity.StructToConfigs(HTTPSchema{})→wfview.ArgForm(rows)→ editor HTML
Adding a new node type touches:
internal/agents/workflow/types.go—NodeTypeconstant + flatNodestruct fieldsinternal/agents/workflow/nodes/<type>.go— executor + exported schema struct +Descriptor()internal/agents/workflow/setup/manager.go— oneeng.Registerlineinternal/tools/agents/workflow/nodes/<type>/meta.go— palette + codec moduleinternal/tools/agents/workflow/nodes/<type>/inspector.templ— inspector partial (one-liner that calls ArgForm)internal/tools/agents/workflow/nodes/<type>/inspector.js— hydrate/save glueinternal/tools/agents/workflow/nodes/all/all.go— blank import the new subpackageinternal/tools/agents/workflow/nodes/static.go— extend//go:embed all:<type>for the JS file
The catalog flow:
eng.Register(workflow.NodeFoo, nodes.NewFooExecutor())
→ engine.Register checks if executor implements engine.Describer
→ calls Descriptor() → stores engine.NodeDescriptor in Engine.Descriptors[t]
→ mcp.NodeTypesCatalog(eng) builds workflow_node_types response from Descriptors map
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.
- 2mo ago First seen · 619 lines · 132 tokens per session scan A c4a967c12fde
workflow-node-module is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed today), licensed MIT. It adds 132 tokens to every session and 8,418 once invoked, about $0.0005 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
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
omh-backend
This is an OMH backend workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…