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/plugin-modulenpx skills add yogasw/wick --skill plugin-modulegit 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.00206 | $0.04736 |
| Opus 5 | $0.00103 | $0.02368 |
| Sonnet 5 | $0.00041 | $0.00947 |
| Haiku 4.5 | $0.00021 | $0.00474 |
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 yesterday.
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 — 330 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.
- yesterday First seen · 330 lines · 206 tokens per session scan A bcf5f4f08edc
plugin-module is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 4d ago), licensed MIT. It adds 206 tokens to every session and 4,736 once invoked, about $0.0010 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
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
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
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.