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/kopp0510/claude-dd/code-simplifiernpx skills add kopp0510/claude-dd --skill code-simplifiergit clone --depth 1 https://github.com/kopp0510/claude-ddWhat 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.00078 | $0.00726 |
| Opus 5 | $0.00039 | $0.00363 |
| Sonnet 5 | $0.00016 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00073 |
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.
What it actually says
Code Simplifier — 官方 agent 包裝器
本 skill 只負責介面層：定範圍 → 調用官方 code-simplifier agent → 呈現結果。 簡化邏輯全在 agent 內，不在此重複。
範圍決定
- 7 步開發迴圈步驟 3（最常見）：範圍 = 該功能段落新增/修改的程式碼（
git diff HEAD~1或使用者指明的段落），不詢問，直接執行 - 使用者指明檔案/目錄/片段：照指示，不追問
- 範圍不明：問一題 —「要簡化哪個範圍？（預設：最近修改的檔案）」，其餘參數用預設
預設不含測試檔；使用者要求才包含。
Agent 調用
依序嘗試 subagent_type：
code-simplifier:code-simplifier（plugin 命名空間）code-simplifier（本地~/.claude/agents/code-simplifier.md）
兩者皆回 Agent type not found → 停下，請使用者跑 ./install-dd-pipeline.sh 補齊。
Prompt 模板：
請簡化以下程式碼，提高可讀性與可維護性，保留所有功能：
範圍：{檔案清單或片段}
重點：降低圈複雜度、改善命名、移除冗餘、簡化條件（early return、減少巢狀）。
約束：不改公開 API 簽名；有測試必須全過。
輸出：簡化摘要 + 關鍵變更的 Before/After 對比。
結果呈現
轉述 agent 的簡化摘要與 Before/After 對比。統計數字只引用 agent 實際回報的， 沒有就不列 — 禁止自行估算複雜度指標。
簡化後提醒（在 7 步迴圈中則直接續行步驟 4）：用 git diff 審查變更，重跑測試確認行為不變。
範圍外
- 架構層重構（模組拆分、設計模式）、效能調校 — 超出簡化範疇，明說不做
- 第三方 / 生成的程式碼 — 不修改
- 效能關鍵段落 — 「看似複雜但高效」的寫法保留，標註說明即可
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 · 53 lines · 78 tokens per session scan A 10be2cdddc38
code-simplifier is a skill published in the GitHub repository kopp0510/claude-dd (6 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 726 once invoked, about $0.0004 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.