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/sourcelin/sourcelin-cloud-blog/sourcelin-ui-refactornpx skills add SourceLin/sourcelin-cloud-blog --skill sourcelin-ui-refactorgit clone --depth 1 https://github.com/SourceLin/sourcelin-cloud-blogWhat 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.00034 | $0.00576 |
| Opus 5 | $0.00017 | $0.00288 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
sourcelin-ui-refactor 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.
What it actually says
Sourcelin UI 重构技能
何时使用
- 编辑
src/modules/** - 编辑
src/shared/** - 编辑
src/app/** - 编辑
src/assets/styles/** - 调整 Naive 集成边界
- 调整架构文档、规则、技能或轻量入口
当前主线目录
src/
app/
modules/
shared/
stores/
assets/styles/{tokens,foundation,naive}
硬边界
- Naive UI 只允许出现在
src/shared/components/ui/**、src/app/App.vue和src/shared/api/http.ts的显式例外中。 - 业务组件和页面不得新增
n-*、glass mixin、:deep(.n-*)、.n-*override 或硬编码颜色。 - 新的共享视觉值必须先进入 Token。
- 导航永远由 route meta 推导,不再维护第二份导航配置。
src/assets/styles/responsive-enhancements.scss当前为兼容层,不应继续扩张为新的主线基础设施。
推荐实现方向
- 页面负责装配
- 页面逻辑优先下沉到
modules/*/composables - 跨模块复用进入
shared/ - 路由由模块
routes.ts导出,并在app/router/index.ts聚合 - API 统一从
modules/*/api/*.api.ts走shared/api/http.ts - 兼容导出优先保留在
stores/*.store.ts,真实实现优先收敛到更清晰的文件名
文档同步要求
当任务影响架构、边界、路由协议、请求约定或样式资产归属时,同时检查:
README.mdAGENTS.mddocs/frontend-architecture.mddocs/style-asset-ledger.mdrules/skills/.cursor/README.md.cursor/rules/project-rules.mdc.opencode/README.md.opencode/skills/
最低验证
npm run typecheck
npm run build
npm run style:guard
npm run test:style-guard
npm run test:architecture
说明
reference.mdREADME.mdAGENTS.mddocs/frontend-architecture.mdrules/
What ships with it
1 file 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.
- 2d ago First seen · 77 lines · 34 tokens per session scan A 8c3afd3e708e
sourcelin-ui-refactor is a skill published in the GitHub repository SourceLin/sourcelin-cloud-blog (20 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 576 once invoked, about $0.0002 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…