Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yogasw/wicknpx agentmods add skills/yogasw/wick/wick-plugin-authoringWrote 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/wick-plugin-authoring)<a href="https://agentmods.dev/skills/yogasw/wick/wick-plugin-authoring"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-plugin-authoring/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/wick-plugin-authoring"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-plugin-authoring.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00130 | $0.02268 |
| Opus 5.5 | $0.00052 | $0.00907 |
| Sonnet 5.5 | $0.00026 | $0.00454 |
| Haiku 4.5 | $0.00013 | $0.00227 |
Grade A, and why
wick-plugin-authoring 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 9d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building a wick plugin
A plugin is a Go package main that wraps ONE module value and calls the kind's serve function. wick runs the binary in its own process. Using plugins (sources, Add new plugin, update, disable, troubleshooting) is covered by the wick-plugins skill — read it for anything past "the zip is built".
1. Pick the kind
| The user wants… | Kind | Lifetime |
|---|---|---|
| Operations an agent or workflow calls (an API wrapper) | connector | spawned on demand, idle-killed |
A page in wick, under /tools/{key}, for signed-in users |
tool | spawned on first request, idle-killed |
| Something that runs on a schedule and returns a markdown result | job | spawned per run, killed when Run returns |
| An always-on HTTP server: webhooks, a public API, SSE, a remote agent | service | always on, restarted on crash; may sleep while idle when it declares AutoOff (see wick-plugin-service) |
Pick the lightest kind that fits. A service is the only kind that keeps in-memory state between requests and the only one reachable without a wick login.
2. Start from the template
Work in a folder that holds connector/ tool/ job/ service/ (the wick repo's plugins/ nested module, or a plugins repo laid out the same way). Copy the template; folders starting with _ are skipped by the tooling.
cp -r service/_template service/my_service # or connector/, tool/, job/
Then:
- Set
Meta.Keyto the folder name.wick plugin buildfails if they differ. Keys are lowercase letters, digits,_and-(not first or last), max 64 characters; use_for new plugins. - Set
VERSION(e.g.0.1.0). It is the plugin version. - Edit the module file (
connector.go,tool.go,job.goorservice.go).main.gonormally stays as is.
3. The contract per kind
| Kind | Module | main.go |
|---|---|---|
| connector | connector.Module (pkg/connector): Meta, Configs, Operations |
wickplugin.Serve(Module()) |
| tool | tool.Module (pkg/tool): Meta tool.Tool, Configs, Register func(r tool.Router) |
toolplugin.ServeTool(Module()) |
| job | job.Module (pkg/job): Meta job.Meta (incl. DefaultCron), Configs, Run func(ctx) (string, error) |
wickplugin.ServeJob(Module()) |
| service | service.Module (pkg/service): Meta, Routes, Configs, CallbackScopes, Register func(mux *http.ServeMux, env *service.Env), RemoteSource |
service.ServeService(Module()) |
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.
- 9d ago First seen · 115 lines · 130 tokens per session scan A a592219f8862
wick-plugin-authoring is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed 3d ago), licensed MIT. It adds 130 tokens to every session and 2,268 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-10-06.
Other skills, from other repositories
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
cloudflare-workers
Build and maintain Cloudflare Workers with typed bindings, explicit compatibility and isolated validation. Use when implementing Workers handlers, integrating KV/R2/D1/Durable Objects/Queues or configuring Wrangler; deployment remains governed by the user task and target environment.
storage-uploads
Implement owned file/object storage and upload/download flows with validated metadata, access and lifecycle. Use when working with S3/R2-compatible storage, attachments or multipart uploads; separate transient transfer state from durable application ownership.
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
edge-computing
Cloudflare Workers, Deno Deploy, Vercel Edge Functions, edge patterns (geo-routing, caching). Use when implementing edge compute, CDN logic, or global low-latency APIs.
api-gateway
API Gateway patterns (Kong, Traefik, AWS API Gateway) — rate limiting, auth, routing, versioning. Use when implementing API gateway, reverse proxy, or API management.