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/simplifynpx skills add caiwuu/Riot --skill simplifygit 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/simplify)<a href="https://agentmods.dev/skills/caiwuu/riot/simplify"><img src="https://agentmods.dev/badge/skills/caiwuu/riot/simplify.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.00057 | $0.00598 |
| Opus 5 | $0.00028 | $0.00299 |
| Sonnet 5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
simplify 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 3d 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
收尾清理
时机：功能已经工作、验证已经过了。先圈范围：
git diff --stat # 这次到底动了哪些文件
[约束] 只清理这次改动碰过的代码。别处的烂代码记下来告诉用户，
不要顺手改——收尾变漫游重构，diff 就没法审了。
清单一：复用
- 新写的函数仓库里是不是已经有了？搜同名、同义词、相邻目录的 utils。 手搓的字符串处理、路径拼接、防抖节流、类型守卫是重灾区。
- 复制粘贴改两行的代码块，统一成一个带参数的。
清单二：质量
- 冗余状态：能从现有状态推导的值不要再存一份——存两份就要同步 两份，忘了同步就是 bug。
- 参数蔓延：给函数加到第 5、6 个参数时，该重构签名了。
- 字符串当类型用：仓库里已有常量、枚举、union 的地方不要写裸 字符串。
- 废话注释：解释「代码做了什么」的删掉（命名已经说了）；叙述 本次改动的删掉（那是 commit message 的事）。只留「为什么这么做」 和代码表达不了的约束。
- 只为这次改动服务的兼容垫片：没人用的旧签名、多余的重导出、 「以防万一」的分支。
清单三：效率
- 重复计算、循环里的重复 IO、N+1 查询；
- 相互独立的异步操作在串行等待（能并发的并发）；
- 无界增长：只进不出的缓存、数组、事件监听器；
- 读整个文件只为用一小段、拉全量列表只为过滤出一条。
修的时候
- 一次一类，每改完一批跑一次测试——清理不该改变行为，测试是 唯一的证明。
- 发现不值得修的就跳过并说一句为什么（比如要大动干戈）。清单是 工具，不是任务。
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.
- 3d ago First seen · 49 lines · 57 tokens per session scan A cbb772316318
simplify is a skill published in the GitHub repository caiwuu/Riot (2 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 598 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…