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/tool-modulenpx skills add yogasw/wick --skill tool-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.00255 | $0.07522 |
| Opus 5 | $0.00128 | $0.03761 |
| Sonnet 5 | $0.00051 | $0.01504 |
| Haiku 4.5 | $0.00026 | $0.00752 |
Grade A, and why
tool-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 2d 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Conventions (tools & jobs) — upstream (wick core)
Scope: this skill is for work on wick itself — modules shipped under
internal/tools/andinternal/jobs/in the wick source tree. If you're building on top of wick in a downstream project (a scaffold generated fromtemplate/, where modules live undertools/andjobs/without theinternal/prefix), use the downstream skill attemplate/.claude/skills/tool-module/SKILL.md— the paths, registration site, and view conventions differ.
Activate this skill whenever the user touches a tool (UI module under internal/tools/) or a job (scheduled worker under internal/jobs/) — creating, improving, fixing, refactoring, restyling, or adding features. The same conventions apply in both directions. When editing an existing module, first audit it against the rules below and bring it up to spec as part of the change; don't leave it half-compliant.
Tools and jobs share one skill because they use the same Config reflection (entity.StructToConfigs with wick:"..." tags), the same widget catalog, and the same boot-time registration pattern — splitting the docs would mean two files drifting out of sync. The only hard differences are the HTTP surface (tools render pages, jobs don't) and the run trigger (tools = request, jobs = cron tick or manual). Read the whole skill once; then the section you need (Tools / Jobs) applies the shared rules to that surface.
Applies to (non-exhaustive triggers)
- "Bikin tool baru X" / "Bikin job baru X"
- "Tambahin fitur Y ke tool X" / "ke job X"
- "Perbaiki bug di tool X" / "di job X"
- "Refactor tool X" / "Refactor job X"
- "Ubah tampilan tool X" / "restyle tool X"
- "Pindahin tool X ke pakai JS"
- Any edit under
internal/tools/{tool}/orinternal/jobs/{job}/(handler, service, view.templ, js/, static.go, config.go) - Changes to
internal/tools/registry.go,internal/jobs/registry.go,internal/pkg/ui/*, or anything that affects how tools/jobs render or register
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.
- 2d ago First seen · 474 lines · 0 tokens per session scan A b6bf543213f5
tool-module is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 5d ago), licensed MIT. It adds 255 tokens to every session and 7,522 once invoked, about $0.0013 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…