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/moberghr/mtk-agent-toolkit/code-simplificationnpx skills add moberghr/mtk-agent-toolkit --skill code-simplificationgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWhat 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.00030 | $0.01322 |
| Opus 5 | $0.00015 | $0.00661 |
| Sonnet 5 | $0.00006 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
code-simplification 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplification
Overview
Simplify only after behavior is proven. The goal is to reduce complexity, remove dead weight, and improve clarity without broadening scope or changing behavior.
When To Use
- After a feature or fix is working
- During a cleanup pass
- When abstractions are heavier than the current use case needs
When NOT To Use
- Before correctness is established
- As cover for a broad refactor unrelated to the task
Workflow
- Start from verified working code.
- Identify the smallest simplifications that improve readability or reduce dead code.
- Remove debug artifacts, dead code, and redundant indirection where safe.
- Collapse premature abstractions that are not earning their cost.
- If dead code is ambiguous or ownership is unclear, ask before deleting.
- Re-run build and tests after the cleanup pass.
Mode: --audit-duplicates
Optional audit that scans the repo for near-duplicate capabilities so they can be consolidated before they multiply. Use the "check before you write" reflex during spec writing; this mode is the periodic sweep that catches duplicates that slipped past it.
- Read
CODE_INDEX.mdat the repo root (template:.claude/references/code-index-template.md). If absent, skip index-guided scanning and note CODE_INDEX.md missing in the report (it is generated duringsetup-bootstrap). - Extract ALL capability rows from the file you already read in step 1 —
this audit needs the full table, so do not enumerate it through
per-keyword queries. Use
bash scripts/query-code-index.sh find "<keyword>"(prints each matching row prefixed with its## <Domain>section) only for targeted follow-up lookups, and fall back togrep -i CODE_INDEX.mdif the script is absent (repo bootstrapped before v7.17). Group near-duplicates by stem (verb + noun) using simple normalization: lowercase, drop suffixes likeAsync/_v2/Impl. - For each cluster of 2+ entries, emit:
- the capability name
- all entry points (path:symbol)
- a one-line recommendation (consolidate / keep separate because …)
- Cross-check with the active stack's coding guidelines — the canonical implementation is usually the one that follows local idioms.
- Output is a findings list, not edits. The engineer decides which clusters to consolidate; consolidation runs through the normal spec flow if it crosses files.
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 · 127 lines · 30 tokens per session scan A 54d62d065f7b
code-simplification is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (6 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 1,322 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.