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/fe-modulenpx skills add yogasw/wick --skill fe-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.00166 | $0.03427 |
| Opus 5 | $0.00083 | $0.01714 |
| Sonnet 5 | $0.00033 | $0.00685 |
| Haiku 4.5 | $0.00017 | $0.00343 |
Grade A, and why
fe-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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FE Module — wick
The fe/ tree is an npm-workspaces monorepo. Shared code lives in fe/common/*
(source-only libraries, no build step); the user-facing apps are Svelte 5 SPAs in
fe/agents/*. Each SPA is mounted by a Go templ "thin shell" that boots the bundle.
Workspaces
fe/
common/ @wick-fe/common-* — source-only shared libraries (no build script)
api/ APIError, WickClientLayer, apiGetE/apiPostE/apiDeleteE, apiGet/apiPost/apiDelete
stores/ toasts, pushToast, dismissToast, toastOk/toastWarn/toastError, snapshotToasts
ui/ ConfirmDialog, ToastHost, Select (exports ONLY the package index)
agents/ @wick-fe/agents-* — full Svelte SPAs (have build/dev/check scripts)
workflow/ Workflow editor
scm/ Git SCM panel
conversation, overview, presets, project-settings, providers, shell, skills, new-session
manager/ @wick-fe/manager — Manager SPA (connector builder, job runner, etc.)
outDir: internal/manager/dist/manager/
Go host: internal/manager/spa.go (NOT internal/tools/)
The workspace globs are ["agents/*", "common/*", "manager"] in fe/package.json.
Shared dev tools (vitest, svelte, @testing-library/svelte, jsdom, typescript, vite)
are declared once at the fe/ root and hoisted — do NOT redeclare them in
common/* packages.
Adding a common library: create fe/common/<name>/package.json with
"main": "src/index.ts" and NO build script, then cd fe && npm install. Pin
runtime deps in that package; leave dev tools to the root.
Adding a new agents SPA: copy fe/agents/workflow/vite.config.ts, change base
and the out dir, add a dev:<app> and build:watch entry to fe/scripts/dev.mjs
workspace list + fe/package.json, then add a templ thin shell (see Routing).
Adding a brand-new Go tool SPA (outside agents): one line —
var spaLoader = spa.New(spaEmbedded, "internal/<path>") (see internal/manager/spa.go).
The spa.Loader handles embed-vs-live-disk, asset-URL resolution, and auto-reload
registration. No init(), no spadev (removed), no per-host reload endpoint.
See § "Go SPA host (internal/pkg/spa)" below.
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 · 307 lines · 166 tokens per session scan A 15d7609dc69f
fe-module is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 5d ago), licensed MIT. It adds 166 tokens to every session and 3,427 once invoked, about $0.0008 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
n8n:design-system
Guidelines on using Design System styles and components. Use when working on .vue files in packages/frontend. Triggers for tasks that include component architecture, styling, UI changes, or feature work.
vue-best-practices
Vue 2/3 代码规范检查。包括组件命名、Props 校验、Composition API 规范等。.
svelte-frontend
Svelte coding guidelines for the Windmill frontend. MUST use when writing or modifying code in the frontend directory.
vue-application-structure
Establishes or reviews the directory layout, component conventions, composable design, Pinia store structure, and Vue Router configuration for a Vue 3 TypeScript application. Invoked when the user asks to structure a Vue app, set up the project layout, or review Vue architecture.
vue-component-design
Designs or reviews Vue 3 component APIs. Handles prop drilling decisions, applies compound component patterns with provide/inject, defines minimal public API surfaces with typed props/emits/slots, and enforces Vue 3.4+ composition conventions. Invoked when creating new components, refactoring existing ones, or…
web
Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override these defaults.