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/n-side-dev/wefa/wefa-vue-frontendnpx skills add n-side-dev/wefa --skill wefa-vue-frontendgit clone --depth 1 https://github.com/n-side-dev/wefaWrote 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/n-side-dev/wefa/wefa-vue-frontend)<a href="https://agentmods.dev/skills/n-side-dev/wefa/wefa-vue-frontend"><img src="https://agentmods.dev/badge/skills/n-side-dev/wefa/wefa-vue-frontend.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.01099 |
| Opus 5 | $0.00044 | $0.00549 |
| Sonnet 5 | $0.00017 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
wefa-vue-frontend 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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeFa Vue Maintainer
This is the maintainer skill for the WeFa Vue library inside this repository.
Load wefa-vue-cookbook first. That cookbook is the shared skill used by consuming projects and by the library itself for common WeFa conventions. Use this skill only for repo-specific maintainer concerns such as exports, Storybook, MDX docs, demo wiring, generated artifacts, tests, and review hygiene inside vue/.
First Reads
- Read
vue/AGENTS.mdfor workspace identity, gotchas, and the repo quality gate. - Read
vue/README.mdfor package capabilities, exports, and workspace scripts. - Read
vue/CONTRIBUTE.mdfor contribution expectations and the npm script surface. - Read
code_review.mdfrom the repo root when the task is a review.
Workspace Map
- Start public-surface discovery at
vue/src/lib.tsandvue/src/containers/index.ts. - Expect feature folders to keep neighbors together: component or container source,
index.ts, stories, MDX docs, and tests in the same folder. - Use
vue/src/locales/index.tsplusvue/src/locales/<locale>/*.jsonfor library i18n wiring. - Check
vue/src/network,vue/src/router,vue/src/plugins, andvue/src/storesbefore adding duplicate helpers. - Treat
vue/src/demoandvue/src/demo/openapias the manual-validation and generated-client surface for demo flows.
Repo-Specific Rules
- New public components or containers should usually ship with source, stories, MDX docs, and unit tests, unless the adjacent feature pattern in this repo clearly differs.
- When a change creates or exposes new public surface, update the nearest
index.tsand shared entrypoints such asvue/src/lib.tsorvue/src/containers/index.ts. - Regenerate or reuse generated OpenAPI client artifacts through the existing script instead of hand-editing generated files.
- Treat
vue/src/demoas a manual-validation surface, not as a place to hide reusable library logic. - Keep
README.md, MDX docs, and Storybook stories aligned with behavior changes that affect consumers. - Respect repo-enforced gotchas from
vue/AGENTS.md, including SFC block order, thewithDefaults()preference, and the rule against Storybookautodocstags.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 67 lines · 87 tokens per session scan A cc5514ac63fa
wefa-vue-frontend is a skill published in the GitHub repository n-side-dev/wefa (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,099 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…