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/tool-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/tool-module)<a href="https://agentmods.dev/skills/yogasw/wick/tool-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/tool-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/tool-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/tool-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 Agent Snooping · line 20 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00000 | $0.07522 |
| Opus 5.5 | $0.00000 | $0.03009 |
| Sonnet 5.5 | $0.00000 | $0.01504 |
| Haiku 4.5 | $0.00000 | $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 2mo 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.
- 2mo ago First seen · 474 lines · 0 tokens per session scan A b6bf543213f5
tool-module is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,522 tokens. 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
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
omh-backend
This is an OMH backend workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…