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/yogasw/wick/wick-workflowsnpx skills add yogasw/wick --skill wick-workflowsgit clone --depth 1 https://github.com/yogasw/wickWhat 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.00078 | $0.01185 |
| Opus 5 | $0.00039 | $0.00593 |
| Sonnet 5 | $0.00016 | $0.00237 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
wick-workflows 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using wick workflows
A workflow is a multi-step automation stored as a JSON graph of typed nodes plus one or more triggers. One inbound event — a Slack mention, a cron tick, a webhook — starts a deterministic, replayable run that wick traces node by node.
A workflow is not an agent; it is the layer above. An agent node inside a workflow spawns an agent turn the same way a channel message would. What the workflow adds is control over when that turn fires, what context it gets, and what happens to its output.
When a workflow is the right answer
| The user wants | Use |
|---|---|
| One-shot chat in Slack / Telegram / web | An agent — channel → pool → reply |
| An LLM that calls APIs | Connectors over MCP |
| A cron that runs a script | A background job |
| One trigger firing a multi-step pipeline — classify the message, branch on intent, fetch from several APIs, hand a focused prompt to an agent, post a structured reply | A workflow |
| Runs you can replay and edit visually | A workflow |
If the task is a single prompt and a single reply, a workflow is overhead. Say so rather than building one.
Anatomy
{
"id": "support-triage",
"version": 1,
"name": "Support Triage",
"enabled": true,
"triggers": [
{
"id": "trigger-slack-message",
"type": "channel",
"channel": "slack",
"event": "app_mention",
"entry_node": "classify_intent"
}
],
"graph": {
"entry": "classify_intent",
"nodes": [
{ "id": "classify_intent", "type": "classify",
"output_cases": ["bug_report", "how_to", "refund"],
"input": "{{index .Event.Payload \"text\"}}" },
{ "id": "bug_report", "type": "agent",
"prompt": "Triage this bug report: {{.Node.classify_intent.input}}" }
]
}
}
Node types include classify, agent, connector, http, shell, branch, parallel, and the datatable_* family. Do not guess a node's schema — fetch it (see Authoring over MCP below).
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.
- 3d ago First seen · 93 lines · 78 tokens per session scan A 48e3c25cc45a
wick-workflows is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 5d ago), licensed MIT. It adds 78 tokens to every session and 1,185 once invoked, about $0.0004 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
omh-buzz
This is a Hermes-native buzz workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
n8n:nathan
Deploy a temporary n8n test instance (or generate a local docker run command) via the internal "Nathan" bot, from the repo instead of Slack. Use after opening a PR to offer the user a live test instance, or whenever someone asks to spin up / deploy a test instance for a branch.
workflow-builder
Load before calling build-workflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, run workflow-sdk validate via workspaceexecutecommand, then call build-workflow with filePath. When…