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/caiwuu/riot/skillifynpx skills add caiwuu/Riot --skill skillifygit clone --depth 1 https://github.com/caiwuu/RiotWrote 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/caiwuu/riot/skillify)<a href="https://agentmods.dev/skills/caiwuu/riot/skillify"><img src="https://agentmods.dev/badge/skills/caiwuu/riot/skillify.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.00061 | $0.00746 |
| Opus 5 | $0.00030 | $0.00373 |
| Sonnet 5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
skillify 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.
What it actually says
沉淀成技能
什么值得沉淀
判据：下次还会做，而且模型光靠常识做不对。
- 这次会话里用户纠正过你的地方——每处纠正都是一条「模型的默认做法 在这里不对」的证据，是技能正文里最值钱的原料；
- 试错试出来的顺序、参数、坑（哪个命令要先跑、哪个 flag 不能省、 哪一步必须等前一步的产物）；
- 用户没有明说、但反复要求的偏好。
反例：模型本来就会的通用流程（「先读文件再改」）写成技能只是噪音， 还占技能清单的位置。
提炼
从会话里回答这几个问题；答不出来的用提问工具问用户，一次问完， 不要挤牙膏：
- 触发场景是什么？这句话就是 description——模型全靠它决定 要不要加载这个技能，写不准等于技能不存在。
- 步骤有哪几步？每步的完成判据是什么（产出什么、怎么算成了）？
- 哪些是硬约束？顺序不能换的、某些文件不能碰的、必须先问用户的。
- 放哪层：只跟这个项目有关 → 项目
.riot/skills/；跨项目通用 → 全局技能目录。
写
- description 写「什么时候用」，不写做法，250 字符以内——超了会被 截断，模型只能在残句上做判断；
- 正文只写模型猜不到的：判据、顺序、坑、约束。每句话问一遍 「删掉它，模型会做错吗」——不会就删；
- 用户纠正过的点写成明确的「不要做 X，因为 Y」，别客气也别含糊；
- 自由度跟着任务的脆弱程度走：多解的任务写原则和判据就够 （审查指南），怕做错的操作写精确的命令和顺序（迁移、发布）。 给脆弱步骤留发挥空间，等于留 bug；
- 别列一堆可选方案让模型现场挑。给一个默认做法，再写清什么 情况下换另一个；
- 大段参考资料（表格、样例、脚本）放技能目录里的独立文件，正文 说明什么时候去读哪个。正文塞满资料，每次加载都是全价，用不用 都付；
- 目录位置、frontmatter 字段、同名优先级这些机制，照 extend-riot 技能的说明来，不要凭记忆写。
写完
把文件路径和 description 给用户过目，说明下一轮对话生效。 提醒一句：设置页能看到技能的解析结果，写坏了那里会显示原因。
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 · 55 lines · 61 tokens per session scan A 6cdb515b4a13
skillify is a skill published in the GitHub repository caiwuu/Riot (14 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 746 once invoked, about $0.0003 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
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…