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/architecture-refactornpx skills add SourceLin/sourcelin-cloud-blog --skill architecture-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.00035 | $0.00571 |
| Opus 5 | $0.00017 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
architecture-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
架构重构技能
使用场景
-
按规则执行渐进式重构。
-
拆分大页面、大组件或大 composable。
-
整理后端模块边界、公共能力、规则体系和文档。
-
对齐
rules/、skills/、AGENTS.md。
输入
-
待重构文件清单或阶段任务。
-
当前规则、技能、目录结构和验证命令。
-
已完成项与剩余项。
输出
-
小步可验证的重构改动。
-
同步更新的规则、技能或 SQL 文档。
-
每步验证结果和剩余风险。
执行步骤
-
读取
AGENTS.md、rules/README.md和全部相关领域规则。 -
确认本轮只处理一个明确边界，避免跨模块大范围改动。
-
先建立或确认自动验证，再修改代码或文档。
-
对前台重构，按页面、组件、composable、API 分层拆分。
-
对后台重构，按查询、表格、分页、弹窗、操作列协议拆分。
-
对后端重构，按 Controller、Service、Mapper、domain、common 边界拆分。
-
对规则体系重构，同步更新
rules/、skills/、AGENTS.md。 -
数据库初始化变化更新
docs/sql/**，架构说明变化更新docs/architecture/**。 -
每个子模块完成后运行对应验证命令，失败先修复再进入下一模块。
依赖 rules
-
rules/api-contract.md -
rules/backend.md -
rules/frontend-platform.md -
rules/frontend-uniapp.md -
rules/frontend-admin.md -
rules/coding-conventions.md -
rules/testing-and-validation.md
禁止行为
-
禁止一次性跨多个无关模块大改。
-
禁止改变视觉表现、交互行为或权限逻辑，除非任务明确要求。
-
禁止为了通过检查删除核心功能或降低测试标准。
-
禁止保留规则、技能、入口文件之间的旧引用。
-
禁止只输出方案不落地验证。
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 · 56 lines · 35 tokens per session scan A 4f9f8edeaa7c
architecture-refactor is a skill published in the GitHub repository SourceLin/sourcelin-cloud-blog (20 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 571 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…