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/yz5e/agent-skills/code-simplifiernpx skills add yz5e/agent-skills --skill code-simplifiergit clone --depth 1 https://github.com/yz5e/agent-skillsWhat 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.00096 | $0.01395 |
| Opus 5 | $0.00048 | $0.00698 |
| Sonnet 5 | $0.00019 | $0.00279 |
| Haiku 4.5 | $0.00010 | $0.00139 |
Grade A, and why
code-simplifier 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplifier
Simplify only the relevant changed code unless the user explicitly asks for a broader sweep. Preserve behavior, outputs, error semantics, side effects, and public interfaces.
Default to a single-agent simplification pass. Use spawn_agent only when the user explicitly asks for delegation, parallel subagents, or a multi-agent review and the touched scope is broad enough to benefit.
Workflow
- Identify the scope.
- Prefer the files or hunks changed in the current task.
- If the scope is unclear, inspect the named function, file, or recent diff.
- Avoid unrelated cleanup outside the touched area.
- Read the project's local conventions.
- Check
AGENTS.md, nearby code, formatter and lint rules, and type patterns. - Match the repository's style instead of forcing a generic one.
- Reuse existing helpers before introducing new abstractions or dependencies.
- Decide whether to delegate.
- Keep the immediate blocking work local. Form a short plan before spawning anything.
- Do not delegate small, tightly coupled, or urgent blocking work where your next step depends on the answer.
- If the user explicitly asks for parallelism and the work is broad enough, use
spawn_agentfor bounded subtasks that can run in parallel with your local work. - Prefer narrow prompts and explicit file or symbol scope over copying the full thread context. Use
fork_contextonly when the subagent truly needs the same conversation history. - Prefer
exploreragents for read-heavy simplification analysis. Reserveworkeragents for implementation only when the write scope can be split into disjoint files or modules.
- Review the code through three simplification lenses.
- Reuse: prefer existing helpers, utilities, and local patterns before adding new abstractions; remove duplication when the shared shape is stable.
- Quality: improve readability, naming, branching, cohesion, and type clarity; preserve logging, validation, and error semantics.
- Efficiency: remove unnecessary work in the touched code such as redundant passes, allocations, awaits, or lookups when the improvement is obvious and behavior stays identical.
- If the lenses conflict, prefer behavioral safety and readability over extra DRYing or micro-optimizations.
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 · 100 lines · 96 tokens per session scan A 5baf90362386
code-simplifier is a skill published in the GitHub repository yz5e/agent-skills (16 stars, last pushed 4mo ago), licensed MIT. It adds 96 tokens to every session and 1,395 once invoked, about $0.0005 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…