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/plugin-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/plugin-module)<a href="https://agentmods.dev/skills/yogasw/wick/plugin-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/plugin-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/plugin-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/plugin-module.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Output Handling · line 268 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00206 | $0.05351 |
| Opus 5.5 | $0.00082 | $0.02140 |
| Sonnet 5.5 | $0.00041 | $0.01070 |
| Haiku 4.5 | $0.00021 | $0.00535 |
Grade A, and why
plugin-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 25d 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Module — connectors (and later tools/jobs) shipped as external plugins
Scope: this skill is the packaging + shipping layer. A plugin's module —
Meta,Configs,Operations,Ctx, thewick:"..."tag grammar, destructive-opt-in,http.NewRequestWithContext, typed responses — is exactly the same as an in-tree connector. For all of that, use theconnector-moduleskill (ortool-modulefor tools). This skill covers only what's different when the module is a separate binary wick downloads and runs, not code compiled into wick.
Mental model: in-tree module vs plugin
| In-tree (connector-module skill) | Plugin (this skill) | |
|---|---|---|
| Lives in | internal/connectors/<name>/ |
plugins/connector/<key>/ (nested module in the wick repo) |
| Registered by | RegisterBuiltins() at compile time |
downloaded → scanned from ~/.<appName>/plugins/connectors/<key>/ at runtime |
| Runs | in the wick process (function call) | own subprocess, gRPC over UDS (hashicorp/go-plugin) |
main() |
none — it's a package | package main → wickplugin.Serve(Module()) |
| Ships as | part of the wick binary | <key>-<ver>-<os>-<arch>.zip (binary + plugin.json) |
The module value is identical — a plugin's connector.Module is built the same
way. The only code difference is the main.go wrapper and that it's a separate Go
module. So: write the connector exactly as connector-module teaches, then wrap +
package per below.
The plugins repo
plugins/
├── go.mod # ONE module; repo-root go.work wires it to local wick
│ # (pkg/plugin isn't in a published wick release yet, so
│ # there is NO `replace` in go.mod — go.work handles it)
├── plugins.json # the marketplace CATALOG (see below)
├── connector/
│ ├── _template/ # scaffold — copy this; skipped by tooling (leading _)
│ │ ├── main.go # wickplugin.Serve(Module())
│ │ ├── connector.go # the connector.Module (this is the connector-module part)
│ │ └── VERSION # source of truth for the plugin version
│ └── httpbin/ # a real, working sample
├── tool/ # (later) kind=tool, same flow
├── job/ # (later) kind=job, same flow
├── README.md RELEASE.md POLYGLOT.md
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.
- 25d ago Changed · +34 lines e72cabe2f6d1
- 1mo ago Changed · +8 lines c3a906c11319
- 2mo ago First seen · 330 lines · 206 tokens per session scan A bcf5f4f08edc
plugin-module is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed today), licensed MIT. It adds 206 tokens to every session and 5,351 once invoked, about $0.0008 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
n8n
Use when the user wants to build, debug, or extend an n8n workflow - generating workflow JSON from a description, scaffolding a custom TypeScript node, building an AI agent (LangChain cluster), iterating over items, writing Code-node JS, linting an existing workflow, diagnosing a failed execution, or driving a live…
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
workflow-builder
Load before calling workflowbuilderbuildworkflow. Use for single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. For any other new workflow, load intent-recognition first when it is listed. Write or edit a workspace source file, then call…
no-code-app
Use when building an app on a no-code/low-code platform (Bubble, Softr, Glide over Airtable or Xano) — picking the platform, modeling the data, keeping usage-metered cost predictable, and planning the exit before lock-in. NOT a hand-written coded app (that is nextjs), NOT wiring SaaS tools together with no app UI…