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-docsnpx skills add yogasw/wick --skill wick-docsgit 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.00064 | $0.00724 |
| Opus 5 | $0.00032 | $0.00362 |
| Sonnet 5 | $0.00013 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
wick-docs 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answering questions about wick
You are running inside wick, but your training data does not contain its current state — features ship weekly. Never answer a wick question from memory. Everything below is a live source; fetch it, then answer. That is what keeps this skill valid without ever being updated.
The documentation site
Base: https://yogasw.github.io/wick/
Start at the machine-readable index:
https://yogasw.github.io/wick/llms.txt
It lists every docs page with a one-line description, grouped by topic (guide, connectors, workflow, reference, …). Pick the relevant page from it — do not guess URLs.
Every page has a raw-markdown twin at the same path with .md appended:
https://yogasw.github.io/wick/guide/introduction.md
Fetch the .md form — clean markdown, no HTML to wade through. There is also
llms-full.txt (every page concatenated); it is large, reach for it only when
a broad question genuinely spans many pages.
"Is there an update?" / "What changed?"
Three sources, use together:
- Running version —
wick versionprints it, if you have a shell. Otherwise the human can read it in the admin panel under Advanced → Software Update, which also has a one-click check. - Latest release —
https://api.github.com/repos/yogasw/wick/releases/latest→tag_name(vX.Y.Z) andpublished_at. Unauthenticated GitHub API is capped at 60 req/hr per IP; on a 403, fall back to the changelog below. - What changed —
https://yogasw.github.io/wick/changelog.md. Newest first; an[Unreleased]section on top holds merged-but-unreleased work. To answer "what's new for me", take the entries between the running version and the latest tag.
Update available = latest tag newer than running version. Report both numbers and the highlights from the changelog range — not just "yes".
Question → source
| Question shape | Fetch |
|---|---|
| what is wick / what can it do | llms.txt, then the introduction + relevant topic pages |
| is there an update / what version | releases/latest + running version |
| what changed / release notes | changelog.md |
| how do I … / how does … work | llms.txt, then that feature's page |
| does wick support X | llms.txt — if no page mentions it, say so; do not invent |
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 · 73 lines · 64 tokens per session scan A 57cc63e8f028
wick-docs is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 724 once invoked, about $0.0003 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…